Release Date: September 03, 2012
Downloading Metro 2.2.1-1
Unless you have already done so, please download the Metro 2.2.1-1 ZIP archive. Once downloaded, you can expand it by executing following shell command:
On Windows or Mac, you may as well just double-click the zip file to expand it.
The expanded metro directory contains following ant files:
These files are used to install the Metro binaries into the respective web containers. The installation procedure is explained in the next section.
Installing Metro 2.2.1-1
GlassFish 3.x bundles Metro by default. You should not update Metro version separately - always update to full Glassfish update.
In case you want to experiment with an unofficial build or release of Metro not available on the official GlassFish 3.x update center or in the official GlassFish update, you may try the GlassFish 3.x installer. To stop GlassFish 3.x instance, install Metro 2.2.1-1 using the standalone installer on top of it and restart the GlassFish 3.x instance, execute the following commands:
asadmin stop-domain <domain-name> ant -Das.home=<GF_INSTALL_DIR> -f <METRO_INSTALL_DIR>/metro-on-glassfish-v3.xml install asadmin start-domain <domain-name>
The installation process for Tomcat is very similar to that of GlassFish v2. Again, the top-level directory of the Tomcat installation is passed as an argument to the ant command. To shutdown Tomcat, change directories, invoke ant, and restart Tomcat by executing these commands:
catalina.sh stop ant -Dtomcat.home=<TOMCAT_INSTALL_DIR> -f <METRO_INSTALL_DIR>/metro-on-tomcat.xml install catalina.sh start
For Tomcat, the installation process copies the two Metro jar files into Tomcat's shared/lib directory. No Tomcat configuration files are modified.
Updating to Metro 2.2.1-1
Once a version of Metro web services stack has been installed on a web container, it can be updated with a new version of the Metro binaries. To update your Metro installation to Metro 2.2.1-1, follow the same steps used for the initial install, shown above.
Note that for GlassFish v2, the second and subsequent installs only update the Metro binaries; no configuration files are modified.
To remove the Metro binaries and configuration changes from your web container, the steps are almost identical to the ones in the installation process. The following steps will restore your web container to the state before Metro installation:
asadmin stop-domain <domain-name> ant -Das.home=<GF_INSTALL_DIR> -f <METRO_INSTALL_DIR>/metro-on-glassfish-v3.xml uninstall asadmin start-domain <domain-name>
catalina.sh stop ant -Dtomcat.home=<TOMCAT_INSTALL_DIR> -f <METRO_INSTALL_DIR>/metro-on-tomcat.xml uninstall catalina.sh start
Metro 2.2.1-1 release consists of following components:
- Metro/WSIT 18.104.22.168 - Browse the WSIT release notes online.
- JAX-WS RI 2.2.7 - Browse the JAX-WS RI release notes online.
- JAXB RI 2.2.6 - Browse the JAXB RI release notes online.
Please subscribe to the users list and send comments/feedbacks/opinions to the list. Additionally, we encourage you to report any bugs you might find while using Metro through our Metro issue trackers.
If you'd like to hack the source code used to build these binaries, please check out the Metro sources running the following command from the command line:
svn export https://svn.java.net/svn/wsit~svn/tags/2.2.1-1 -r 7272 metro-sources