|
|
|
|
|
Implementing JAX-WS 2.0 efficiently requires substantial changes from JAX-RPC because data binding is delegated to JAXB and extreme care is needed to retain, or improve, performance. This challenge is also an opportunity to better support non-textual encodings, like FastInfoset, multiple transports, like SMTP, and features like Interoperability with WCF. Kohsuke writes about these challenges and opportunities in Neck Deep in JAX-WS. |
The new architecture is being discussed in the DEV JAX-WS Mailing List; check the Call for Participation. The architectural changes are not for the main trunk but rather are planned for the next revision (also see the current architecture documents).
