...

<web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1"
         xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.2"
         xmlns:naming="http://geronimo.apache.org/schemas-2.1/docs/geronimo-naming-1.2">

    <sys:environment>
        <sys:moduleId>
            <sys:groupId>default</sys:groupId>
            <sys:artifactId>geronimo-web-6</sys:artifactId>
            <sys:version>1.0</sys:version>
            <sys:type>car</sys:type>
        </sys:moduleId>
    </sys:environment> 

    <naming:abstract-naming-entry xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="naming:persistence-unit-refType">

        <naming:persistence-unit-ref-name>messagedrivenbean-persistenceunitref-unitrefname</naming:persistence-unit-ref-name>
        <naming:persistence-unit-name>messagedrivenbean-persistenceunitref-unitname</naming:persistence-unit-name>

    </naming:abstract-naming-entry>


</web-app>

<naming:

...

message-

...

destination>

The <naming:ejbmessage-ref>destination> XML element uses the Geronimo Naming namespace, which is used to identify the common elements
for resolving EJB references, resource references, and Web services references, which is documented here:

• http://geronimo.apache.org/schemas-2.1/docs/geronimo-naming-1.2.xsd.html

The <naming:ejbmessage-ref>destination> element is used to map EJB references to EJB's in other applications using remote home and remote interface. The application which contains the EJB being referenced should either be in same EAR or should be included in dependency list of this application. Also note as the EJB's referenced are in a different JVM all the Client interfaces should also be included in the current application.

<naming:ejb-local-ref>

configure a JMS queue or topic which acts like a destination for the messages delivered.

<security-realm-name>

The <security-realm-name> The <naming:ejb-local-ref> XML element uses the Geronimo Naming namespace, which is used to identify the common elements for
resolving EJB references, resource references, and Web services references, default namespace for the geronimo-web.xml file, which is documented here:

• http://geronimo.apache.org/schemas-2.1/docs/geronimo-namingweb-2.0.1.2.xsd.html^{Image Modified}.

The <naming:ejb<security-localrealm-ref>* name> element is used to map EJB references to EJB's in other applications using local home and local interface. The application which contains the EJB being referenced should either be in same EAR or should be included in dependency list of this application. Also note as the EJB's referenced are in a different JVM all the client interfaces should also be included in the current application.

<naming:service-ref>

specify the name of the security realm that will be used for user authentication.

<app:security>

The <app:security> The <naming:service-ref> XML element uses the Geronimo Naming namespace, which is used to identify the common elements for
resolving EJB references, resource references, and Web services references, Applicaiton namespace, which is documented here:

• http://geronimo.apache.org/schemas-2.1/docs/geronimo-namingapplication-12.20.xsd.html^{Image Modified}.

The <naming:service-ref> <app:security> element is used to map service references to service's in other applications. The application which contains the EJB being referenced should either be in same EAR or should be included in dependency list of this application.

<naming:resource-ref>

maps roles specified in the WAR file to roles or principals in the security realm that will be used after deploying the module.

<sys:service>

The <sys:service> The <naming:resource-ref> XML element uses the Geronimo Naming namespace, which is used to identify the common elements for
resolving EJB references, resource references, and Web services references, System namespace, which is documented here:

• http://geronimo.apache.org/schemas-2.1/docs/geronimo-namingmodule-1.2.xsd.html^{Image Modified}

The <naming<sys:resource-ref>service> element is used to map resource references to resources's like JDBC resources, JMS resources, etc. configured outside the current application.

<naming:resource-env-ref>

an empty generic element to be extended by GBean and other module types.

<ee:persistence>

The <ee:persistence> XML element uses the Java EE Persistence namespaceThe <naming:resource-env-ref> XML element uses the Geronimo Naming namespace, which is used to identify the common elements for
resolving EJB references, resource references, and Web services references, which is documented here:

• http://geronimojava.apachesun.org/schemas-2.1/docs/geronimo-naming-1.2.xsd.html^{Image Removed}

The <naming:resource-env-ref> element is used to map resource references to administrative objects deployed as a part of connectors.

<naming:message-destination>

• com/xml/ns/persistence/^{Image Added}

Apache Geronimo uses OpenJPA for providing Java Persistence API to Java EE applications deployed in the server.

<sys:gbean>

The <sys:gbean> The <naming:message-destination> XML element uses the Geronimo Naming namespace, which is used to identify the common elements
for resolving EJB references, resource references, and Web services references, System namespace, which is documented here:

• http://geronimo.apache.org/schemas-2.1/docs/geronimo-namingmodule-1.2.xsd.html^{Image Modified}

The <naming:message-destination> element is used to configure a JMS queue or topic which acts like a destination for the messages delivered.

<security-realm-name>

It is used to define GBean(s) that are configured and deployed with the web application.. These additional Geronimo services will be deployed when the application is deployed (and stopped when the application is stopped). Normally, the implementation classes for these services are included at the server level and referenced using a dependency element.

JNDI References:

More information and details about JNDI can be found here: JNDI.

<naming:ejb-ref>

The <naming:ejb-ref> element uses the Geronimo Naming namespace, which is used to identify the common elements for resolving EJB references, resource references, and Web services references, which is documented here:

• http://geronimo.apache.org/schemas-2.1/docs/geronimo-naming-1.2.xsd.html^{Image Added}

The <naming:ejb-ref> element is used to map EJB references to EJB's in other applications using remote home and remote interface. The application which contains the EJB being referenced should either be in same EAR or should be included in dependency list of this application. Also note as the EJB's referenced are in a different JVM all the client interfaces should also be included in the current application.

<naming:ejb-local-ref>

The <naming:ejb-local-ref> XML element uses the Geronimo Naming namespace, which is used to identify the common elements for
resolving EJB references, resource references, and Web services referencesThe <security-realm-name> XML element uses the Geronimo default namespace for the geronimo-web.xml file, which is documented here:

• http://geronimo.apache.org/schemas-2.1/docs/geronimo-webnaming-1.2.0.1.xsd.html^{Image Modified}.

The <security<naming:ejb-realmlocal-name>ref> element is used to specify the name of the security realm that will be used for user authentication.

<app:security>

to map EJB references to EJB's in other applications using local home and local interface. The application which contains the EJB being referenced should either be in same EAR or should be included in dependency list of this application. Also note as the EJB's referenced are in a different JVM all the client interfaces should also be included in the current application.

<naming:service-ref>

The <naming:service-ref> The <app:security> XML element uses the Geronimo Applicaiton Naming namespace, which is used to identify the common elements for
resolving EJB references, resource references, and Web services references, which is documented here:

• http://geronimo.apache.org/schemas-2.1/docs/geronimo-

...

• naming-1.2

...

• .xsd.html^{Image Modified}

...

The <app:security> element <naming:service-ref> is used to maps roles specified in the WAR file to roles or principals in the security realm that will be used after deploying the module.

<sys:service>

to map service references to service's in other applications. The application which contains the EJB being referenced should either be in same EAR or should be included in dependency list of this application.

<naming:resource-ref>

The <naming:resource-ref> The <sys:service> XML element uses the Geronimo System Naming namespace, which is used to identify the common elements for
resolving EJB references, resource references, and Web services references, which is documented here:

• http://geronimo.apache.org/schemas-2.1/docs/geronimo-modulenaming-1.2.xsd.html^{Image Modified}

The <sys<naming:service>resource-ref> element is an empty generic element to be extended by GBean and other module types.

<ee:persistence>

The <ee:persistence> XML element uses the Java EE Persistence namespace, which is documented here:

• http://java.sun.com/xml/ns/persistence/^{Image Removed}

Apache Geronimo uses OpenJPA for providing Java Persistence API to Java EE applications deployed in the server.

<sys:gbean>

used to map resource references to resources's like JDBC resources, JMS resources, etc. configured outside the current application.

<naming:resource-env-ref>

The <naming:resource-env-ref> XML element uses the Geronimo Naming namespace, which is used to identify the common elements for
resolving EJB references, resource references, and Web services referencesThe <sys:gbean> XML element uses the Geronimo System namespace, which is documented here:

• http://geronimo.apache.org/schemas-2.1/docs/geronimo-modulenaming-1.2.xsd.html^{Image Modified}

It The <naming:resource-env-ref> element is used to define GBean(s) that are configured and deployed with the web application.. These additional Geronimo services will be deployed when the application is deployed (and stopped when the application is stopped). Normally, the implementation classes for these services are included at the server level and referenced using a dependency element.

...

map resource references to administrative objects deployed as a part of connectors.

Samples

For example, the following web.xml and geronimo-web.xml are the deployment descriptor and Geronimo deployment plan respectively, of a web application that connects to a datasource deployed on DB2 and retrieves data from a table.

...