The JAX-WS team is pleased to announce general availability of JAX-WS 2.1 RI. We have put tremendous effort in bringing this where it is! Besides cool features and JAX-WS 2.1 API, two main architectural changes that went in to this release - Performance and Extensibility. JAX-WS 2.1 RI is built on Java standards such as JAX-WS -2.1 (JSR 224), JAXB 2.1 (JSR 222), SAAJ, StAX and whole bunch of related Java standards. Not only that, the Web Services standards and profiles compliance is at the core - from tools to the complete runtime system. The important thing about JAX-WS 2.1 RI is that it is a complete re-architecture and re-write of JAX-WS 2.0. We did it for two main reasons - to make it high performing and extensible! See the reason we did it and also our 2.0.1 M1 release with these architectural changes and merge of 2.0.1 into 2.1. JAX-WS 2.1 RI brings in new productivity features and also extension APIs for the middleware developers to enhance JAX-WS 2.1 with their custom extensions, such as WSIT, Open JBI component, and Glassfish v2. Key Features

• Reference Implementation (RI) of JAX-WS 2.1. Full JAX-WS 2.1 Specification compliance
• Development Tools
  • WSDL to Java generator
    • Wsimport command 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, SOAP Binding and WSDL Binding
  • WS-Addressing - Member Submission
  • SOAP 1.1 and 1.2
  • REST and XML/HTTP
  • WS-I Basic Profile 1.1, Simple SOAP Binding Profile 1.0 and 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 JAX-WS 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.2 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
    • JAX-WS 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 JAX-WS 2.1 RI bundle
    • Bundled with JDK 6
  • Any other container that supports Servlet 2.4, such as Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!

See Vivek's blog for performance data and other details.

Sweet!

Congratulations! We are very pleased to see the Spring support. This is very cool, and a neat use of the new Spring 2.0 XML schema extension mechanism. Rod Johnson Interface21 - Spring from the Source: Support, Training, Consulting

Will this be part of jdk6u1? -- Luis Neves

I don't remember any case where update releases of JDK picked up a new version of a component specification. So I suspect it will be bit unlikely.

I don't remember any case where update releases of JDK picked up a new version of a component specification. So I suspect it will be bit unlikely.

I hope to see a change of policy. I tried to use the new JAX-WS libraries and tools with jdk6 without success. There is more to it than simple copying some jars to the endorsed directory.

I hope you find this posting useful: http://weblogs.java.net/blog/kohsuke/archive/2007/02/running_jaxbws.html

The Spring integration is very interesting. Moreover we can use Jax-WS on Tomcat - jetty - jboss servers, it is very good! Michele