JAX-RPC 2.0 Early Draft
It looks like I've already been scooped by Eduardo but just in case you missed that, the first early draft of JAX-RPC 2.0 is now available for review. It addresses the following goals and requirements:
- Integration with JAXB
- Addition of client side asynchrony
- Improved support for document and message centric usage
- Improvements to the handler framework
- Default alignment with the WS-I Basic Profile
- Improved protocol neutrality
Of these, integration wih JAXB is the most significant departure from previous versions of JAX-RPC. Earlier versions defined their own mapping between XML and Java data structures but in JAX-RPC 2.0 all data binding functionality is delegated to JAXB 2.0 while JAX-RPC still handles mapping between Java and WSDL constructs. This separation of responsibilities allows a developer to resuse code between JAXB and JAX-RPC based applications or to easily extend an existing JAXB based application to use JAX-RPC facilities. It also provides JAX-RPC with full support for XML Schema where previously only a subset was required to be supported.
Other significant additions inlcude a new document-centric API for dynamic Web service invocation, support for dynamic and type-safe client side asynchrony and several improvements to the handler framework including protocol agnostic handlers.
This early draft is still a work in progress, subsequent versions of the specification will address the following additional goals and requirements:
- Support for WS-I Basic Profile 1.1 and Attachments Profile 1.0
- Support for SOAP 1.2
- Support for WSDL 2.0
- Versioning and evolution of web services
- Web services security
- Integration with JSR 181 (Web Services Metadata)
- Service endpoint model
- Runtime services
The expert group solicits your input on the current draft, details of where to send comments are included in the specification.