Links: Table of Contents | Single HTML | Single PDF

Release Notes

Table of Contents

1. Required Software
2. Installation Instructions
3. Running on top of JDK 6
4. Jar dependency
5. Current Limitations / Bugs / Issues
6. Changelog

1. Required Software

  • Requires JDK 6 or later

  • Requires Ant 1.7.1 or later

  • Tested with GlassFish v4.x and Apache Tomcat 5.5.20

2. Installation Instructions

The following applies to the JAX-WS standalone bundles.

  • Extract JAX-WS RI 2.3.0-SNAPSHOT bundle

  • To use with GlassFish

    • Glassfish contains JAX-WS within Metro package so no installation required. For updating JAX-WS installation in Glassfish please refer to Metro project.

  • To install on Tomcat

    • Set CATALINA_HOME to your Tomcat installation.

    • Run

      ant install

      This essentially copies lib/*.jar from the root of JAX-WS RI extracted bundle to $CATALINA_HOME/shared/lib

    • If you are running on top of JDK6, run

      ant install-api

      or use

      ant -help

      for detailed information.

If you intend to only invoke an already existing Web service, then alternatively you can use the wsimport and wsgen scripts in the bin directory of the JAX-WS RI 2.3.0-SNAPSHOT bundle.

3. Running on top of JDK 6

JDK includes JAX-WS and JAXB API and RI. JAX-WS RI 2.3.0-SNAPSHOT includes RI of JAX-WS/JAXB 2.2. In order to run JAX-WS RI 2.3.0-SNAPSHOT you would need to specify ONLY jaxws-api.jar, and jaxb-api.jar jars using the Java Endorsed Standards Override Mechanism

4. Jar dependency

Table 1. Jar dependencies summary

Runtime Jars

FastInfoset.jar, jaxb-api.jar, jaxb-core.jar, jaxb-impl.jar, jaxws-api.jar, javax.annotation-api.jar, jaxws-rt.jar, jsr181-api.jar, mimepull.jar, javax.xml.soap-api.jar, saaj-impl.jar *, stax2-api.jar, woodstox-core-asl.jar, stax-ex.jar, streambuffer.jar, policy.jar, gmbal-api-only.jar, management-api.jar, ha-api.jar

Tooltime Jars

All the runtime jars + jaxb-xjc.jar, jaxb-jxc.jar, jaxws-tools.jar

If you run JAX-WS RI 2.3.0-SNAPSHOT with IBM JDK, there are two options:

  • to add Oracles's JAXP implementation jars along

  • to remove the saaj-impl.jar from the libraries in order IBM SAAJ implementation to be used

JAXWS also depends on resolver implementation form JDK, which is not found on AIX. The repackaged resolver.jar can be found in the distribution, or Maven though. First approach is recommended.

5. Current Limitations / Bugs / Issues

  • The java.util.Collection classes 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.

  • Although JAX-WS customizations are portable across implementations, the names of WSDL and schema files generated are not specified. Therefore each vendor may and most likely will generate different names. Therefore, when switching between implementations of JAX-WS, it may be necessary to modify your customization files to reflect different WSDL and schema file names.

  • This holds true for different releases of the JAX-WS RI. The JAX-WS RI may in each release change these file names to resolve bugs. If and when this does occur, a developer would need to change the filenames in their customization files to match the new file names.

6. Changelog