About EJB Files Generated by JDeveloper

When you create Enterprise JavaBeans in JDeveloper, you'll use the modeling tools and wizards. The EJB wizards are used to:

Create the Enterprise Bean class for several types of Enterprise JavaBeans: Container Managed Persistence (CMP) entity beans, Bean Managed Persistence (BMP) entity beans, stateless session beans, stateful session beans, and message-driven beans (MDB).
Generate the home interface needed to create an EJB object. The inclusion of the ejbCreate() method allows you to deploy the EJB to Oracle9iAS immediately, without having to manually code the method.
Enable a selection of home interface methods (and create a default method).
Generate the remote interface.
Enable a selection of remote interface methods.

When using the EJB wizards, you cannot create new methods to include in the home and remote interfaces. The EJB Wizard defines one create() method by default for the home interface. To add or remove other methods in the EJB class, you can run the modeler or the EJB Module Editor to select the methods to expose in the Bean interfaces.

The EJB Wizards will create a basic class that contains only the methods required to implement the bean interface. The remote and home interfaces are derived from this class.

When you create an EJB using the EJB Wizard, JDeveloper generates the following classes for you:

EJB classes
- Enterprise Bean class
- Home interface (optional)
- Remote interface (optional)
- Optionally, a Local Interface
- Optionally, a class for entity Beans
ejb-jar.xml Deployment Descriptor
- orion-ejb-jar.xml file

About the Enterprise Bean Class and Interface Classes

When you create an EJB with the wizard, JDeveloper creates an EJB folder which contains the Enterprise Bean class, home interface, and remote interface for the EJB. This folder appears as a subfolder in the System Navigator with the same name you provided as the EJB remote interface in the EJB Wizard.

About the ejb-jar.xml Files

The ejb-jar.xml file specifies attributes of the bean including transactional properties, and provides instructions for the EJB container about how the bean expects to interact with the container. The ejb-jar.xml file is generic - it doesn't contain any application server-specific properties.

JDeveloper can generate ejb-jar.xml files specific to an application server. The orion-ejb-jar.xml file is generated by default, and is used for deployment to OC4J. To generate a container-specific file for WebLogic, select WebLogic Deployment Descriptor from the Enterprise JavaBeans category in the New dialog box.

WebLogic Persistence Files

If you choose WebLogic as your persistence provider, the following two files are generated:

weblogic-ejb-jar.xml - this file contains generic descriptor information.
weblogic-cmp-rdbms-jar.xml - this file contains information about CMP entity beans only.

For more information, see Using WebLogic As a Persistence Manager.