Difference: GeronimoNotes (22 vs. 23)

Revision 2303 Aug 2007 - TobyCabot

Line: 1 to 1

META TOPICPARENT	name="JavaNotes"

The Apache group's j2ee server is called Geronimo. Here are some notes.

Line: 42 to 42

Deployment

Changed:

<
<

Runs using a standalone application jar called target/bin/deployer.jar. The startup class specified in MANIFEST.MF is org.apache.geronimo.deployment.cli.DeployTool. DeployTool parses the command line parameters and delegates to org.apache.geronimo.deployment.cli.ServerConnection to do most of the work. ServerConnection starts up a small kernel and loads a configuration into that kernel. Among the gbeans loaded into that kernel is one that wraps the org.apache.geronimo.deployment.Deployer class. Deployer picks apart the jar file and builds the various bits and pieces.

If the thing being deployed is an ear file then Deployer will end up calling org.apache.geronimo.j2ee.deployment.EarConfigBuilder.

wiki page here: http://wiki.apache.org/geronimo/Deployment

j2ee xml descriptor files (and their geronimo counterparts) are unmarshalled into java classes using apache xmlbeans (http://xml.apache.org/xmlbeans).

For resource adapters, the ConnectorModuleBuilder class builds the configuration that gets deployed at run-time.

Stack trace at startup (setting a RA parameter), heavily edited to remove the gbean/mbean cruft:

        at skeleton.ra.spread.AdapterImpl.setConfigParameter(AdapterImpl.java:84)
        at org.apache.geronimo.connector.ResourceAdapterWrapper.setAttribute(ResourceAdapterWrapper.java:130)
        at mx4j.server.MX4JMBeanServer.registerMBean(MX4JMBeanServer.java:729)
        at org.apache.geronimo.kernel.Kernel.loadGBean(Kernel.java:255)
        at org.apache.geronimo.kernel.config.Configuration.doStart(Configuration.java:176)
        at org.apache.geronimo.gbean.jmx.GBeanMBean.doStart(GBeanMBean.java:593)
        at org.apache.geronimo.gbean.jmx.AbstractManagedObject.startRecursive(AbstractManagedObject.java:303)
        at mx4j.server.MX4JMBeanServer.invoke(MX4JMBeanServer.java:1079)
        at org.apache.geronimo.gbean.jmx.AbstractManagedObject.startRecursive(AbstractManagedObject.java:310)
        at org.apache.geronimo.kernel.Kernel.startRecursiveGBean(Kernel.java:275)
        at org.apache.geronimo.system.main.Daemon.main(Daemon.java:137)

In 1.2, the cli code is in the modules/geronimo-deploy-tool directory. It ends up in the lib/ directory and the repository, but the version in lib seems to take precedence. If you're making changes you can build in modules/geronimo-deploy-tool then copy the jar from the maven repo to the target lib directory, i.e.

$ cp ~/.m2/repository/org/apache/geronimo/modules/geronimo-deploy-tool/1.2-SNAPSHOT/geronimo-deploy-tool-1.2-SNAPSHOT.jar ~/target/lib/

>
> Runs using a standalone application jar called target/bin/deployer.jar. The startup class specified in MANIFEST.MF is org.apache.geronimo.cli.deployer.DeployerCLI.

EJB

View topic | History: r26 < r25 < r24 < r23 | More topic actions...