Check for a behavior change for EJB bean presence in a web module

Starting with the Java EE 6.0 specification, you can deploy an Enterprise JavaBeans (EJB) bean in a web module. Because web project Java source files are compiled to .class files and are packaged under the WEB-INF/classes folder, Java files that are annotated with EJB annotations behave as an EJB bean in WebSphere Application Server Version 8.0. If a Java archive (JAR) file in the WEB-INF/lib folder contains a class that has an EJB annotation, that class also behaves as an EJB bean in WebSphere Application Server Version 8.0 and Liberty.

This rule flags the following items in web projects with a version of 2.5 or later:

• EJB annotations in Java files
• EJB annotations in JAR files
• A web.xml file when the project contains an ejb-jar.xml file in the same WEB-INF folder

The rule scans for the following EJB annotations:

• javax.ejb.MessageDriven
• javax.ejb.Singleton
• javax.ejb.Stateful
• javax.ejb.Stateless

Note: If the web.xml file is not available, the rule assumes that the version is 2.5 or later.

The rule does not flag items in the following cases:

• If the project is not a web project
• If the web project does not have a version of 2.5 or later
• If the <web-app> element in the web.xml file contains the metadata-complete="true" attribute, and no ejb-jar.xml file is located in the WEB-INF folder

For additional information, see the following resource:

• EJB content in WAR modules