This will give you an opportunity to play with the source code. The build will also deploy the sample application into a Geronimo server.
You may choose an already unpacked and/or running server to deploy this sample application.
Alternatively, you may let the build download the latest Geronimo binary and unpack it.
By default, a downloaded server binary will be unpacked into the sample project's target
directory.
Or you may choose a different installation directory.
You may let the build download the geronimo binary from a remote repository or point it to an already downloaded binary.
By default, it will download a Geronimo binary with the jetty webcontainer. You may however choose the Geronimo binary with the tomcat webcontainer.
Steps:
- if you don't have Maven v2.0.4 already, download that from Apache's maven site. Add maven's bin directory to your path.
- Download the sample source zip and unpack it.
If your platform is Windows, it is recommended that you unpack the zip in a directory quite close to the root to prevent a Windows restriction on long path name.
- go to the directory where the sample source code has been unpacked
- execute the command
mvn site
- execute the command
mvn
Some optional arguments:
- -DgeronimoHome: path to directory where a server has already been unpacked.
- -DinstallDirectory: path to directory where a server has to be unpacked. If one already exists there, a later one, if available, will be downloaded and installed.
If a later binary isn't available, the existing server is started. If one doesn't exist, then the downloaded one will be unpacked here.
- -DassemblyId: [jetty | tomcat] by default, Geronimo with the jetty webcontainer will be downloaded and started. Set the value of this to tomcat for the tomcat webcontainer.
- -DassemblyArchive: path to an assembly archive already downloaded.
- start the server using
startServer.bat
or startServer.sh
- open a browser and go to the sample's context root.