JAX-WS ${IMPL_VERSION} ${IMPL_VERSION_SUFFIX} is a Web Services framework that provides tools and infrastructure to develop Web Services solutions for the end users and middleware developers.

Reference Implementation (RI) of JAXWS ${SPEC_VERSION} API. Full JAX-WS ${SPEC_VERSION} compliance
Development Tools
- WSDL to Java generator
  - Wsimport comman line tool, ant task and Maven2 plugin
- Java to WSDL generator
  - Wsgen command line tool, ant Task and Maven2 plugin
- Integrated with NetBeans 5.5.1
Standards
- Web Services Addressing 1.0 - Core
- Web Services Addressing 1.0 - SOAP Binding
- Web Services Addressing 1.0 - WSDL Binding (RI specific support)
- WS-Addressing - Member Submission
- SOAP 1.1 and 1.2
- REST and XML/HTTP
- WS-I Basic Profile 1.1
- WS-I Simple SOAP Binding Profile 1.0
- WS-I Attachment Profile 1.0
- MTOM
Extensions (May not be final unless says so)
- Web Services Interoperable Technologies ( WSIT) - enables .NET 3.0 interoperability
  - WS-ReliableMessaging
  - WS-Policy
  - WS-MEX
  - WS-Security/WS-Security Policy
  - WS-Trust/WS-Secure Conversation
  - WS-AT/WS-Tx (Supported only on Glassfish v2)
  - SOAP/TCP
- Spring support
- Pluggable Transport
  - In-VM transport
  - Servlet transport (bundled with the RI)
  - JMS transport
  - SOAP over TCP transport (part of WSIT)
- FastInfoset (bundled with JAXWS 2.1 RI)
  - ITU-T Rec. X.891 | ISO/IEC 24824-1
- JBI Service Engine and Binding Component(part of Glassfish v2)
- HTTP Binding Component, used by Open JBI component
Data binding - JAXB 2.1.3 RI
Server Side Asynchrony - AsyncProvider
Stateful Web Services
Support for custom WebServiceFeature
Hosting API
- These APIs can be used by a J2EE application server to integrate JAX-WS 2.1 RI for hosting JAX-WS services
Endpoint Deployment
- Glassfish v2
  - Tightly integrated with Glassfish
  - Supports EJB and Web endpoints
  - 109 based deployment support for better portability
  - JAXWS RI specific deployment descriptor support
- Sun One Application Server 9.0 ur1
- Light weight HTTP server
  - On JDK 1.5 through http.jar distributed with the JAXWS 2.1 FCS RI bundle
  - Bundled with JDK 6
- Any other container that supports Servlet 2.4, such as Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!

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 JAXWS RI specific APIs. JAXWS ${IMPL_VERSION} ${IMPL_VERSION_SUFFIX} has many bug fixes made for interoperability with .NET 3.0. This is made mostly possible due to WSIT, which uses JAXWS plugabble architecture to plug in support for WS-Metadata, WS-Policy, WS-ReliableMessaging, WS-Transaction, WS-SecureConversation and WS-Security.

If you wish to use JAX-WS ${IMPL_VERSION} ${IMPL_VERSION_SUFFIX} RI 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 Glassfish documentation/samples. The majority of the documentation included with JAX-WS is valid with Java EE 5 as well.

The documentation for JAX-WS ${IMPL_VERSION} ${IMPL_VERSION_SUFFIX} as well as the sample applications will be periodically updated in the JAX-WS project.

The architecture document describing the latest JAXWS ${IMPL_VERSION} ${IMPL_VERSION_SUFFIX} can be found here.

Please go to http://jax-ws.dev.java.net for the latest documentation and samples.

Requires JDK 5.0 Update 2 or later
Requires Ant 1.6.2 or later
Tested to work with Glassfish Promoted Build v2 41a (Beta 2 Candidate 2) and Apache Tomcat 5.x

The following applies to the JAX-WS standalone bundles.

Extract JAX-WS ${IMPL_VERSION} ${IMPL_VERSION_SUFFIX} bundle
Install on Glassfish v2
- Glassfish v2 Beta2 Candidate2 has JAX-WS RI integrated and is pretty close to JAX-WS ${IMPL_VERSION} ${IMPL_VERSION_SUFFIX} so you do not need to do anything. If you still want to use the JAX-WS ${IMPL_VERSION} ${IMPL_VERSION_SUFFIX} overriding the one with Glassfish v2 follow the instructions for installing it on top of Sun One Application Server 9.0 Update 2
Install on Sun One Application Server 9.0 Update 2
- Set AS_HOME to the installation directory of Glassfish
- cd to the root directory of the extracted JAXWS RI bundle
- Set JAXWS_HOME to the root directory of the extracted JAXWS RI bundle
- Invoke '$ANT_HOME/bin/ant install' to install JAXWS RI jar on the applciation servers - Glassfish v1/v2 or Sun One AS 9.0 UR1
Install on Tomcat
- Copy lib/*.jar from the root of JAXWS extracted bundle to $TOMCAT_HOME/shared/lib

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 ${IMPL_VERSION} ${IMPL_VERSION_SUFFIX} bundle.

JDK 6 includes JAXWS 2.0 and JAXB 2.0 API and RI. JAX-WS ${IMPL_VERSION} ${IMPL_VERSION_SUFFIX} includes newer and enhanced APIs of JAXWS/JAXB 2.0. In order to run JAX-WS ${IMPL_VERSION} ${IMPL_VERSION_SUFFIX} you would need to put jaxws-api.jar, jaxb-api.jar, jsr173_api.jar and saaj-api.jar.

Copy $JAXWS_HOME/lib/jaxws-api.jar to $JDK6_HOME/jre/lib/endorsed directory
Copy $JAXWS_HOME/lib/jaxb-api.jar to $JDK6_HOME/jre/lib/endorsed directory
Copy $JAXWS_HOME/lib/jsr173_api.jar to $JDK6_HOME/jre/lib/endorsed directory
Copy $JAXWS_HOME/lib/saaj-api.jar to $JDK6_HOME/jre/lib/endorsed directory

For details see Endorsed Directory Mechanism. Above, JAXWS_HOME points to the root directory of the extracted JAXWS RI bundle. JDK6_HOME points to JDK 6 installation directory.

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, 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

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.

Bug fixes

Changes from JAXWS 2.0 RI

Bug 6475032 This bug was introduced in JDK 1.5_07 and the fix will be available in JDK 1.5_12 in second quarter 2007. You should not see if you are using JDK 1.5_06.
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.

Go to http://jax-ws.dev.java.net.

Send your feedback to users@jaxws.dev.java.net or use the JAXB 2.0 and JAXWS 2.0 forum.