Last Modified: December 9th, 2005
This release implements JSR 261, the JavaTM API for XML Web Services Addressing (JAX-WSA) 1.0 specification. The current pre-release version of the JAX-WSA RI requires a special, modified version of the JAX-WS 2.0 libraries (.jar files). These special versions are included with this bundle.
The documentation for JAX-WSA 1.0 as well as the sample applications will be periodically updated in the JAX-WSA project on java.net. Please refer to http://jax-wsa.dev.java.net for the latest documentation and samples.
Requires JDK 5.0 Update 2 or later
Requires Ant 1.6.2 or later
Requires Sun Java System Application Server Platform Edition 8.1, Glassfish (the Sun-sponsored Open Source Java EE 5 Application Server) or Tomcat (the Apache Servlet/JSP Container) v5.5 or later
The Java API for XML Web Services Addressing 1.0 (JAX-WSA) specification [1] defines APIs and a framework to enable the transport neutral mechanisms to address Web services and messages. These mechanisms are defined by the W3C WS-Addressing Core 1.0 Candidate Recommendation, W3C WS-Addressing 1.0 - SOAP Binding Candidate Recommendation and W3C WS-Addressing 1.0 - WSDL Binding Working Draft specifications. The JAX-WSA specification and implementation align with the Java API for XML Web Services 2.0 (JAX-WS) to define these APIs and framework. Please reference the JAX-WSA 1.0 specification for a detailed description of the programming model and APIs.
The following applies to the JAX-WSA standalone bundles. If you have installed JAX-WSA as part of JWSDP 2.0, then installation is complete.
For a stand-alone JAX-WSA bundle, its component jars must first be
installed to the Application Server in order to build and deploy a
web service. To do this, set AS_HOME to the
installation directory of the Application Server. Next, you need to
invoke the command ant install from within the root
directory of the extracted bundle. This will install the
JAX-WSA binaries into the Application Server.
In this pre-release version, using Logical and Protocol Handlers to process WS-Addressing headers is not supported.
WS-Addressing is always turned on
irrespective of the presence of wsaw:UsingAddressing
extensibility element in the WSDL.
Operation is not dispatched based
upon the wsa:Action header.
Only "http://"-style namespaces are supported.
Few changes have been made in the APIs and programming model since the Early Draft 1 of the specification. These changes are still being discussed within the JSR 261 Expert Group and will show in a future version of the specification. These changes are highlighted in the bundled javadocs.
Of the pre-defined faults in W3C WS-Addressing 1.0 - SOAP Binding, only "Action Not Supported" fault is supported.
If ENDPOINT_ADDRESS_PROPERTY property in BindingProvider's request context is changed, then it is not reflected in wsa:To header for the outgoing SOAP message. (See Issue #2 for more details).
Reference parameters received on the client-side are not
available in AddressingContext. (See Issue
#5 for more details).
For the latest on JAX-WSA technology, go to http://jax-wsa.dev.java.net.
Please use the JAX-WSA users mailing list for feedback.