Contents of Application.ear File

The .ear file that is produced has the following structure and contents:

• META-INF Directory

  The META-INF Directory includes the following:

  • application.xml

    This file is automatically generated and lists the mapping of EJB modules to JAR files that are contained in the application.

  • MANIFEST.MF

    This file details the contents of the .ear file.

• Core .jar Files

  The core .jar files include¹:

  • appinf.jar
  • appinf_internal.jar
  • coreinf.jar
  • rules.jar
  • jde_commons.jar
  • log4j.jar
  • commons-pool.jar
  • commons-codec.jar
  • commons-discovery.jar
  • jdom.jar
  • axis.jar
  • castor.jar
  • jaxrpc.jar
  • saaj.jar
  • java_cup.zip
  • InfrastructureModule.jar
  • InvalidationModule.jar
  • DBtoJMS.war
  • ClientModule.war
• Facade .jar Files

  These are only present if facade generation has been enabled. All facades defined in the application are packaged into one .jar file, FacadeModule.jar. This .jar file contains the bean implementation classes for the EJB modules that represent the facades. The .jar file contains the following files in the META-INF directory:

  • ejb-jar.xml

    This file is automatically generated and contains the definition of every EJB module contained in the .jar file. All the publicly available methods are listed and the details of the resources available to the EJB modules.

  • weblogic-ejb-jar.xml

    Generated WebLogic Server specific deployment descriptor.

  • Manifest.mf

    The manifest file, detailing the classpath for the EJB.

• Other .jar Files

  The other .jar files contain the generated and hand crafted code from the application. These include struct.jar, application.jar, workflow.jar, implementation.jar and properties.jar. The properties.jar file contains the Bootstrap.properties file. This is the file containing the machine specific configuration properties for initially getting a connection to the database.