Java EE validators

This table lists the Java™ EE validators that are available for the different project types and gives a brief description of each validator.
Validator name Description
Application client 5.0 and 6.0 Validator The application client 5.0 and 6.0 validator validates the following application client project resources:
  • Main-Class: Main: If no main class is defined, this error appears in the Problems view: The Main-Class attribute must be defined in the application client module.
  • EJB Reference: EJB Reference name cannot be empty.
  • Service Reference: Service Reference name cannot be empty.
  • Message Destination Reference: Message Destination Reference name cannot be empty.
  • Resource Reference: Resource Reference name cannot be empty.
  • Resource environment reference: Resource environment reference name cannot be empty.
EJB 3.0 and 3.1 validator The EJB 3.0 and 3.1 validator verifies that enterprise beans contained in an EJB project comply with the Sun Enterprise JavaBeans Specifications (3.0 and 3.1), depending on the level of the bean. Specifically, the EJB validator validates the following resources:
  • EJB project contains at least one bean (created in a deployment descriptor or using annotations).
  • Deployment descriptor validation only:
    • Session bean ejb-class is specified and exists.
    • Message bean ejb-class is specified and exists.
    • The following classes specified for each session bean in the deployment descriptor exist:
      • Business local interface
      • Business remote interface
      • Home interface
      • Local interface
      • Local Home interface
      • Remote interface
      • Service endpoint
    • All interfaces and classes listed in references exist:
      • EJB references (ejb-ref and ejb-local-ref)
        • Local
        • Local Home
        • Home
        • Remote
        • Injection classes
      • resource references
        • Injection classes
      • message destination references
        • Injection classes
      • Service references
        • Service interface
        • Injection classes
    • Duplicate references do not exist.
    • Security role is not empty.
    • Duplicate Security Roles do not exist.
EAR 5.0 and 6.0 validator The EAR 5.0 and 6.0 validator validates the following:
  • Each module, including utility jars, are backed by a physical resource.
  • The Context root of each Web module is unique.
  • Module URIs: Web URIs end with .war, connector URIs end in .rar, other URIs end in .jar (Applies for Deployment Descriptor case only).
  • Duplicate URIs do not exist. Two modules with web1.war cannot exist. customer.war and customer.jar are allowed.
  • Security roles cannot be empty.
  • Duplicate security roles do not exist.

The EAR validator only ensures the validity and dependency of the module projects with respect to the enterprise application project.

Web 2.5 and 3.0 validator The Web 2.5 and 3.0 validator validates the following items relating to the deployment descriptor:
  • Servlet class exists.
  • Duplicate servlets do not exist.
  • Servlet mapping is not duplicated.
  • All interfaces and classes listed in references exist.
  • Duplicate references do not exist.
  • Security role is not empty.
  • Duplicate Security Roles do not exist.

Feedback