Javadoc
For an ear without an application.xml, determine modules via:
a. All ear modules with an extension of .war are considered web modules. The
context root of the web module is the name of the file relative to the root
of the application package, with the .war extension removed.
b. All ear modules with extension of .rar are considered resource adapters.
c. A directory named lib is considered to be the library directory, as
described in Section�EE.8.2.1, �Bundled Libraries.�
d. For all ear modules with a filename extension of .jar, but not in the lib
directory, do the following:
i. If the JAR file contains a META-INF/MANIFEST.MF file with a Main-Class
attribute, or contains a META-INF/application-client.xml file, consider the
jar file to be an application client module.
ii. If the JAR file contains a META-INF/ejb-jar.xml file, or contains any
class with an EJB component annotation (Stateless, etc.), consider the JAR
file to be an EJB module.
iii. All other JAR files are ignored unless referenced by a JAR file
discovered above using one of the JAR file reference mechanisms such as the
Class-Path header in a manifest file.