Page History

...

<openejb-jar
 	xmlns:openejb="http://openejb.apache.org/xml/ns/gopenejbopenejb-jar-2.2"
 	targetNamespace="http://openejb.apache.org/xml/ns/gopenejbopenejb-jar-2.2"
 	xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.2"
 	xmlns:security="http://geronimo.apache.org/xml/ns/security-2.0"
 	xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.2"
 	xmlns:pkgen="http://openejb.apache.org/xml/ns/gpkgen-2.1"
 	version="1.0">
 	...
 </openejb-jar>

...

The <ejb-ql-compiler-factory> XML element uses the OpenEJB default namespace for a openejb-jar.xml file, which is documented here:

• http://openejb.apache.org/xml/ns/gopenejbopenejb-jar-2.2.xsd.html^{Image Modified}

The <ejb-ql-compiler-factory> element is used to specify the name of a Java class that can compile EJB-QL (Query Language) queries into SQL statements for a particular database product. This must be the fully-qualified class name of a class that implements org.tranql.sql.EJBQLCompilerFactory. The default is for the Derby database, which ships with Geronimo, although it may work for other database products as well. An example openejb-jar.xml using the <ejb-ql-compiler-factory> XML element is shown:

...

The <db-syntax-factory> XML element uses the OpenEJB default namespace for a openejb-jar.xml file, which is documented here:

• http://openejb.apache.org/xml/ns/gopenejbopenejb-jar-2.2

The <db-syntax-factory> element is used to specify the name of a Java class that can customize CMP SQL statements for a particular database product. This must be the fully-qualified class name of a class that implements org.tranql.sql.DBSyntaxFactory. The default is for the Derby database, which ships with Geronimo, although it may work for other database products as well. An example openejb-jar.xml using the <db-syntax-factory> XML element is shown:

...

The <enforce-foreign-key-constraints> XML element uses the OpenEJB default namespace for a openejb-jar.xml file, which is documented here:

• http://openejb.apache.org/xml/ns/gopenejbopenejb-jar-2.2

The <enforce-foreign-key-constraints> element is effectively a true/false element – if it's present that means true, and if it's not present, that means false. If true, then Geronimo will make a special effort to execute insert, update, and delete statements in an order consistent with the foreign keys between tables. If false, then Geronimo will execute statements in any order, though still within the same transaction. This element should be present if the underlying database enforces foreign keys at the moment a statement is executed instead of at the end of the transaction. An example openejb-jar.xml setting the <db-syntax-factory> XML element to "true" is shown:

...

The <relationships> XML element uses the OpenEJB default namespace for a openejb-jar.xml file, which is described here:

• http://openejb.apache.org/xml/ns/gopenejbopenejb-jar-2.2.

Container-managed relationships are initially defined in the ejb-jar.xml deployment descriptor, but the mappings to specific database elements are defined in the openejb-jar.xml file using the <relationship> element.

...

Unless otherwise noted, all the Common, EJB Entity, EJB Session, and EJB Message-driven elements use the OpenEJB default namespace for a openejb-jar.xml file, which is documented here:

• http://openejb.apache.org/xml/ns/gopenejbopenejb-jar-2.2

<enterprise-beans>

The <enterprise-beans> element used to specify references by <entity>, <session>, or <message-driven> EJB's. For example, a EJB Entity Bean would be specified similarly as below in an openejb-jar.xml file:

...