...
Once a security realm is deployed, it's available for any JEE5 application deployed in Apache Geronimo to map declared roles to actual users/groups through a Geronimo deployment plan.
Resources
Applications
An enterprise application archive (EAR) can consist of several application modules. The application modules can be Web Application Archives (WAR) , EJB modules (JAR), application client modules (JAR) or Resource Archive modules (RAR). User can either deploy these modules individually or bundle them into a single EAR file and deploy the EAR file.
When deployed individually, each application module should accompany a Geronimo deployment plan to map declared resources names, ejb names, security roles, JMS roles to corresponding actual entities deployed in the server. The Geronimo deployment plans also contain any Geronimo specific settings and configurations. When deployed as a single bundle (EAR), user can create a single Geronimo deployment plan to accomplish all the mappings, settings and configurations.
The following table summarizes different JEE5 modules and corresponding Geronimo deployment plans accompany themDepending on the type of application you are deploying you will need a different type of deployment plan. The following table illustrates the standard JEE deployment descriptors as well as those specific to Apache Geronimo.
File | Standard JEE deployment descriptors | Apache Geronimo specific Deployment plan |
---|---|---|
Enterprise Web Application Archive application archive (WAREAR) | web application.xml xm | geronimo-webapplication.xml |
Enterprise Web application archive Application Archive (EARWAR) | application web.xml | geronimo-applicationweb.xml |
J2EE Connector resources archive (RAR) | ra.xml | geronimo-ra.xml |
J2EE client application archive (JAR) | client.xml | geronimo-application-client.xml |
JAR containing EJBs | ejb-jar.xml | openejb-jar.xml |
...