DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
Error formatting macro: scrollbar: java.lang.NoClassDefFoundError: com/opensymphony/webwork/ServletActionContext
This section summarizes how to develop Geronimo deployment plans for different Java EE 5 modules.
- Annotations
- Configuring resources in the application scope
- Creating deployment plans for EJB applications
- Creating deployment plans for enterprise applications
- Creating deployment plans for Java EE application clients — A Java EE client module requires application-client.xml as deployment descriptor and geronimo-application-client.xml as deployment plan.
- Creating deployment plans for Java Persistence API
- Creating deployment plans for Web applications — A Web application requires web.xml as deployment descriptor and geronimo-web.xml as deployment plan.
- Naming (JNDI) — This page describes how the Geronimo server puts the names of JCA objects and EJBs in the JNDI namespace so that clients may access them.
- Client JNDI Names — The openejb.jndiname.format property allows you to supply a template for the global JNDI names of all your EJBs. With it, you have complete control over the structure of the JNDI layout can institute a design pattern just right for your client apps. See the Service Locator doc for clever ways to use the JNDI name formatting functionality in client code.
- Datasource, ConnectionFactory, MDB and JPA Naming
- EJB naming
- Global JNDI
- JNDI environment references