< Zurück | Inhalt | Weiter >

23.3.2 Geronimo

Geronimo will be undergoing lots of change between the time that we write this and the time that you read this. Be sure to check the Geronimo Web site1 for the latest information.

Geronimo deployment is done as a separate executable step and is not folded into the server. This separation of functions keeps the server smaller and quicker on startup. The deployer has the smarts for reading in all the XML configuration information for your bean, building all the needed classes, and serializing it to package it up.

To deploy our EAR, we execute the following command from the Geronimo home directory:


$ java -jar bin/deployer.jar --install --module budgetpro.ear



image

1. http://geronimo.apache.org/


Although not available in the early releases, Geronimo may add a “hot deploy” feature where the EAR file can just be put into a deploy directory and the rest will happen automatically. Even so, what will be happening behind the scenes is this same deploy step.


23.4 MAINTAINING A DISTRIBUTED APPLICATION


The deployment is easy if you have the EAR file built properly. But as you just saw, that can be a big “if”—the EAR consists of several layers of files that must be in the right place and have the right contents. There are tools to help with all this, though. Ant is widely used to automate many of these tasks.