|Metro||Users Guide||Tools||JAX-WS Extensions||Samples||Metro Community|
Metro 1.1.1 is a Web Services framework
that provides tools and infrastructure to develop Web Services solutions for the
end users and middleware developers.
2. Features in this release
This release brings in the highly pluggable framework through abstractions such as Tube and Message. Refer to the latest architecture document . This architecture document is a glorified javadoc which includes all the JAX-WS RI specific APIs. Metro 1.1.1 has many bug fixes made for interoperability with .NET 3.0. This is made mostly possible due to WSIT, which uses JAX-WS plugabble architecture to plug in support for WS-Metadata, WS-Policy, WS-ReliableMessaging, WS-Transaction, WS-SecureConversation and WS-Security.
wish to use Metro 1.1.1 in a Java EE container in a Java EE portable manner you need to use the
standard Java EE 5 deployment descriptor; please refer to the
Java EE 5 or
documentation/samples. The majority of the documentation included with JAX-WS is
valid with Java EE 5 as well.
3. Online Documentation
The documentation for Metro 1.1.1 as well as the sample applications will be periodically updated in the JAX-WS project.
The architecture document describing the latest Metro 1.1.1 can be found here .
Please go to
latest documentation and samples.
4. Required Software
Requires JDK 5.0 Update 2 or later
Requires Ant 1.6.2 or later
Tested to work with Glassfish v2 UR1 and Apache Tomcat 5.x
The following applies to the JAX-WS standalone bundles.
'$ANT_HOME/bin/ant install'to install Metro jar on the applciation servers - Glassfish v1/v2 or Sun One AS 9.x
If you intend to only invoke an already existing Web service, then
alternatively you can use the
scripts in the
bin directory of the Metro 1.1.1 bundle.
6. Running on top of JDK 6
JDK 6 includes JAX-WS 2.0 and JAXB 2.0 API and RI. Metro 1.1.1 includes newer and enhanced APIs of JAX-WS/JAXB 2.0. In order to run Metro 1.1.1 you would need to put jaxws-api.jar, jaxb-api.jar, jsr173_api.jar and saaj-api.jar.
For details see
Directory Mechanism. Above, METRO_HOME points to the root directory of the
extracted Metro bundle. JDK6_HOME points to JDK 6 installation directory.
7. Jar dependency
|Runtime Jars||FastInfoset.jar, activation.jar, http.jar, jaxb-api.jar, jaxb-impl.jar, jaxws-api.jar, jaxws-rt.jar, jsr173_api.jar, jsr181-api.jar, jsr250-api.jar, mimepull.jar, resolver.jar, saaj-api.jar, saaj-impl.jar, sjsxp.jar, stax-ex.jar, streambuffer.jar|
|Tooltime Jars||All the runtime jars + jaxb-xjc.jar, jaxws-tools.jar|
java.util.Collectionclasses cannot be used with rpc/literal or document/literal BARE style due to a limitation in JAXB. However, they do work in the default document/literal WRAPPED style.
Changes from JAX-WS 2.1.2 RI
11. Known Bugs/Issues
Go to http://jax-ws.java.net.
Send your feedback to firstname.lastname@example.org or use the Metro and JAXB Forum