Oracle Application Server 10g: J2EE Deployment and Administration

About orion-ejb-jar .xml

Some very simple EJB applications can be deployed without any special configuration beyond their standard ejb-jar.xml descriptors. However, in most cases, you'll need to map JNDI locations, resource references, EJB references, security settings, and so on in orion-ejb-jar.xml , which is packaged in META-INF/ along with ejb-jar.xml .

This server-specific descriptor does the following:

• Maps JNDI locations for the EJBs as well as other resources and components they reference.

• Configures timeouts, pool sizes, and other performance settings.

• Configures persistence for both stateful session beans and entity beans, in particular, it allows for the mapping of container-managed fields and relationships.

• Configures finder method queries.

• Specifies transactional behavior.

• Configures value-added features, including OR mapping and Active Components for Java (AC4J).

• Configures role mappings and other security settings.

• Allows the overriding of environment entries and other elements in ejb-jar.xml .

• Configures CORBA security settings for EJBs accessed over RMI-IIOP.

The document type declaration (DTD) used for the orion-ejb-jar.xml deployment descriptor can be found on Oracle's website at http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd . The deployment descriptor should always start with a header like this:

<?xml version = '1.0' encoding = 'windows-1252'?> <!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd">

The overall structure of the deployment descriptor as defined by this DTD is shown in Figure 11-1.

Figure 11-1: XML-SPY diagram

Overall Structure

The root element <orion-ejb-jar> has two attributes (used internally by the server) and two subelements: one for EJB deployments ( enterprise-beans ), and one for security role mapping ( assembly-descriptor ). The elements are listed in Table 11-1.