Table of Contents
Reference Implementation (RI) of JAX-WS 2.2.9 API. Full JAX-WS 2.2.9 compliance
The following applies to the JAX-WS standalone bundles.
Extract JAX-WS RI 2.2.8 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.2.8 bundle.
JDK 6u4 includes JAX-WS 2.1 and JAXB 2.1 API and RI.
JAX-WS RI 2.2.8 includes RI of JAX-WS/JAXB 2.2. In order to run
JAX-WS RI 2.2.8 you would need to specify ONLY
jaxws-api.jar
, and
jaxb-api.jar
jars using the Java
Endorsed Standards Override Mechanism
Table 1. Jar dependencies summary
Runtime Jars |
|
Tooltime Jars | All the runtime jars +
|
If you run JAX-WS RI 2.2.8 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
First approach is recommended.
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.
2.2.3
2.2.1
2.2
Add WS-Addressing 1.0 Metadata support as per 2.2 spec
Support for @XmlElement
on SEI's
wrapper parameter
Support for @XmlType
on exception
classes
Implement HTTP SPI
Implement Endpoint API with features
Generate new constructors in the generated Service class(service level features, wsdllocation)
Add
support for customizing wrapper wsdl:part
names as defined in 2.2
Add
support for customizing wsdl:message
name
using @WebFault
as defined in
2.2
Fault customization should accept fully qualified name of the exception class to be generated
Customization of Service should accept fully qualified class name
XPath expressions in jax-ws customization can now select multiple nodes
Disable server-side exception stacktrace for service specific exceptions
wsimport now handles URL redirection of imported wsdls correctly
2.1.7
2.1.6
2.1.5
2.1.4
2.1.3
2.1.2
JMX Agent for the server side
Mtom Interop with .NET 2.0/WSE 3.0
2.1.1
JAXB 2.1 RI Integration
JAX-WS 2.1 MR (JSR 224) implementation
Type substitution support
WS-Addressing - W3C and Memeber Submission
APIs to create EPR and use it to invoke endpoint
Support for enabling/disabling features, such as WS-Addressing/MTOM
Asynchronous server
Tubes and Fiber for asynchronous message processing
Dispatch<Message> and Provider<Message>
Stateful Webservice support