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. While Windup 1 looked at each resource individually, Windup 2 creates relationships between resources in order to provide further context for Windup pattern matching. This allows for much more advanced application profiling, 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

Traditionally, this was not possible because Windup looked at each resource as individuals. Windup 2's Graph Subsystem allows profilers to create relationships between resources. Let's see how Windup's Graph is modified by each visitor.

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