Arun Gupta, Miles to go ...
Arun Gupta is a technology enthusiast, a passionate runner, and a community guy who works for Sun Microsystems.
Friday August 25, 2006
JSR 261 (Java API for XML
Web Services Addressing, JAX-WSA) has been operating
under the assumption that it would layer on top of JAX-WS
2.0 (JSR 224). This enabled us to provide WS-Addressing functionality
without delaying the JAX-WS 2.0 EG. The plan was to later make this JSR into a
required component of a future version of the Java web services stack.
After looking at the current state of JSR 261 and listening to the feedback we
received from community, this API seems to provide a rich and powerful API for
WS-Addressing that is more targeted to stack implementers rather than to the end
developer. In order to simplify the programming model for WS-Addressing for JAX-WS
developers, we are revisiting those initial assumptions at the first available
opportunity, namely the upcoming JAX-WS 2.1 Maintenance Release (MR).
We are converging the JSR 261 specification and API with the upcoming
JAX-WS 2.1 MR. Here is a top-level summary of the proposed changes:
- Simpler abstraction of EndpointReference as a first-class citizen in JAX-WS.
- Standard way to enable WS-Addresing in JAX-WS using @BindingType.
- Various JAX-WS APIs expose/consume EPR.
- Action/FaultAction moved from JSR 261 to JAX-WS MR.
The proposals are being discussed with JSR 261 and JSR 224 EG. Since
all the relevant functionality from JSR 261 will be incorporated in the JAX-WS
MR, this would also mean that JSR 261 will be withdrawn from the JCP.
We believe this approach is the right thing to do for the specifications, the
platform and the community. Leave a comment or send your feedback.
Technorati: JSR JCP JAX WSA JAXWS WSAddressing Web Services
Posted by Arun Gupta in webservices | Comments[3]
|
|
|
|
|
| |
This is a personal weblog, I do not speak for my employer.
