Skip to content
Brad edited this page Mar 25, 2014 · 17 revisions

One of the major goals of Windup 2 was to further the application profiling capabilities. Windup 1.x treats each resource as an individual. This limited the tool because many times in Java EE, meta data is stored in XML (or multiple XMLs) that is relevant to a Java class, for example. Windup 2's Graph Subsystem allows profilers to create relationships between resources, which provides much more advanced application profiling capabilities, including:

  • Java Classloader Profiling
    • Blacklist Class Profiling (transitively)
    • ClassNotFound Profiling
    • Duplicate Class Profiling
  • EJB Profiling
  • Spring Configuration Profiling
  • Hibernate Configuration Profiling
  • Archive Dependency Profiling
  • JNDI Resource Profiling
  • JMS Resource Profiling
  • Database Resource Profiling
  • JMX Object Name Profiling

Let's see how Windup's Graph is enhanced by each visitor.

  1. ArchiveEntryIndexVisitor
  2. JavaClassVisitor
  3. XmlResourceVisitor
  4. EjbConfigurationVisitor
  5. HibernateConfigurationVisitor
  6. HibernateMappingVisitor
  7. SpringConfigurationVisitor
  8. ManifestVisitor
Clone this wiki locally