Page History

...

The <sys:environment> XML element uses the Geronimo System namespace, which is used to specify the common elements for common
libraries and module-scoped services, which and is documented here:

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

...

The <context-root> XML element uses the Geronimo default namespace for the geronimo-web.xml file, which and is documented here:

• http://geronimo.apache.org/schemas-2.1/docs/geronimo-web-2.0.1.xsd.html

...

The <work-dir> XML element uses the Geronimo default namespace for the geronimo-web.xml file, which and is documented here:

• http://geronimo.apache.org/schemas-2.1/docs/geronimo-web-2.0.1.xsd.html

...

The <naming:web-container> 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 and is documented here:

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

...

<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">

    <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> 

    <container-config>

        <tomcat xmlns="http://geronimo.apache.org/xml/ns/web/tomcat/config-1.0">
            <host>testhost.com</host>
            <valve-chain>FirstValve</valve-chain>
            <tomcat-realm>TomcatRealm</tomcat-realm>
        </tomcat>

    </container-config>

</web-app>

...

<security-

...

realm-

...

name>

The <naming:abstract<security-namingrealm-entry>name> 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 default namespace for the geronimo-web.xml file, and is documented
here:

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

The <abstract<security-namingrealm-entry>name> element is an abstract element used as a generic element for referencing these reference types:

...

An example geronimo-web.xml file is shown below using the <abstract-naming-entry> element to reference a persistence unit:

...

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

<app:security>

The <app:security> XML element uses the Geronimo Applicaiton namespace, and is documented here:

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

The <app:security> element 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>

The <sys:service> XML element uses the Geronimo System namespace, and is documented here:

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

The <sys:service> 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, and is documented here:

• http://java.sun.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> XML element uses the Geronimo System namespace, and is documented here:

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

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:

All the JNDI reference elements in this section use the Geronimo Naming namespace, which is used to identify the common elements for resolving EJB references, resource references, and Web services references, and is documented here:

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

Additionally, more information and details about JNDI references can be found here: JNDI.

<naming:abstract-naming-entry>

The <abstract-naming-entry> element is not technically a JNDI reference element. It is included in this section because it is an abstract element used for containing these JNDI reference types:

• <gbean-ref>
  
  The <gbean-ref> element is used to map GBean references to GBeans configured outside the current module
  
  
• <persistenceunit-ref>
  
  The <persistenceunit-ref> element is used to map persistence unit references to persistence units configured outside the current module
  
  
• <persistencecontext-ref>
  
  The <persistencecontext-ref> element is used to map persistence context references to persistence contexts configured outside the current module

An example geronimo-web.xml file is shown below using the <abstract-naming-entry> element to reference a persistence unit:

<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>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<artifactId>geronimo-web-6</sys:type>artifactId>
        </sys:moduleId>
    <<sys:version>1.0</sys:environment> version>

    <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><sys:type>car</sys:type>
        <naming:persistence-unit-name>messagedrivenbean-persistenceunitref-unitname</naming:persistence-unit-name>

    </naming:abstract-naming-entry>


</web-app>

<security-realm-name>

The <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-web-2.0.1.xsd.html^{Image Removed}.

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

<app:security>

The <app:security> XML element uses the Geronimo Applicaiton namespace, which is documented here:

• http://geronimo.apache.org/schemas-2.1/docs/geronimo-application-2.0.xsd.html^{Image Removed}.

The <app:security> element 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>

The <sys:service> XML element uses the Geronimo System namespace, which is documented here:

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

The <sys:service> 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>

The <sys:gbean> XML element uses the Geronimo System namespace, which is documented here:

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

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 references 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:

...

</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:pattern>
            <naming:groupId>messagedrivenbean-persistenceunitref-pattern-groupid</naming:groupId>
            <naming:artifactId>messagedrivenbean-persistenceunitref-pattern-artifactid</naming:artifactId>
            <naming:version>messagedrivenbean-persistenceunitref-pattern-version</naming:version>
            <naming:module>messagedrivenbean-persistenceunitref-pattern-module</naming:module>
            <naming:name>messagedrivenbean-persistenceunitref-pattern-name</naming:name>
        </naming:pattern>
    </naming:abstract-naming-entry>

</web-app>

<naming:ejb-ref>

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 references, which is documented here:

...

<naming:ejb-local-ref>

The <naming:ejb-local-ref> 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>

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, which is documented here:

...

in the current application.

<naming:service-ref>

The <naming:service-ref> 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>

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, which is documented here:

...

of this application.

<naming:resource-ref>

The <naming:resource-ref> 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>

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 references, which is documented here:

...

.

<naming:resource-env-ref>

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

<naming:message-destination>

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, which is documented here:

...

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

...