JAXWS 2.0.1 M1, a.k.a. re-architected JAXWS 2.0 RI is out! These bits are also delivered with the Glassfish 9.1 v2. So you can get all the improvements we made in JAXWS 2.0.1 right from this glassfish download.

JAXWS 2.0.1 M1 is significantly modified since JAXWS 2.0 FCS. So what does this re-architecture brings in:

Performance

Performance boost - 70% compared to JAXWS 2.0 FCS. See Sameer's blog for the details on JAXWS 2.0.1 M1 performance. Here is what we did to boost performance:

• Revisited some of the key abstractions
  • Message and Pipe as the central abstraction
• More supporting abstractions
  • Encoder, Decoder, TransportFactory, ...
• Reduced # of special-purpose interface
  • No performance penalty when not used
  • No more custom hook for JavaEE

Pluggability

Based on abstractions - Message and Pipe. WSIT  components use this pluggable architecture to enable WS-Security, WS-Trust, WS-Relaible Messaging, WS-Addressing, etc.

A typical pipeline on the client side would look like:

Similarly a server pipeline would look like:

The Pipe line is assembled based on the binding, handler or policy assertions.

WSIT  components use this pluggable architecture to enable WS-Security, WS-Trust, WS-Relaible Messaging, WS-Addressing, WS-Policy, WS-MetadataExchange etc.

See Jitu's blog on JAXWS transports which are written as Pipe.

JAXWS 2.0.1 M1 is feature complete with respect to the previous JAXWS 2.0 FCS release. We have run all the JAXWS 2.0 FCS SQE and TCK tests and found more than 90% of tests passing. So its stable but there are still few open P3 bugs.

Download Glassfish 9.1 v2  thats released today, it has JAXWS 2.0.1 M1 bits in it.  See Carla's blog on this release. So try out and send us your feedback.

You can also download JAXWS 2.0.1M1 directly from java.net and tryout with other servlet containers as well. Checkout the doucmentation for details.