- The name was misleading. Developers were assuming that the "RPC" in JAX-RPC referred to XML-RPC, instead of Web Services.
- The new name helps prevent JAX-RPC 1.x users from assuming that a migration to JAX-RPC 2.0 would be entirely seamless, as the new version has a number of fundamental changes in dependencies and bindings.
- The new classification away from "JAX-RPC" removes the need for maintenance of legacy API classes, which makes the new development cleaner.
Doug Kohlert writes, in "JAX-RPC 2.0 renamed to JAX-WS 2.0," that JAX-RPC has been renamed to reflect a shift from "Java API for XML-Based RPC" to "Java API for XML-based Web Services," for three reasons:
- Posted by: Joseph Ottinger
- Posted on: May 25 2005 07:42 EDT
- NOW it all makes sense by Fred McCann on May 25 2005 10:52 EDT
- JAX-RPC isn't only RPC by Deivson Rayner Teixeira da Costa on May 25 2005 13:18 EDT
- It never was about XML-RPC! by John Vance on May 25 2005 14:07 EDT
- JAX-RPC 2.0 renamed to JAX-WS 2.0 by eduardo pelegri-llopart on May 25 2005 17:59 EDT
- Javapedia by Sean Sullivan on May 31 2005 00:27 EDT
Ever since JAX-RPC 1.1 isn't only RPC!
JAX-WS is appropriate.
JAX-RPC has no, and never had, support for XML-RPC ( http://www.xmlrpc.org ). It always was a SOAP stack, and of course it still is. They incorporated various WS-* specifications (like WS-security) and rolled it all into the Web Services Developer Pack. TheServerSide gets more and more like Slashdot, please at least try to get the basic facts right. Thanks.
"JAX-RPC 2.0 (Java API for XML Based RPC)", this is quoted from the original blog.
"XML based RPC" and XML-RPC, how close the names are before the renaming. No wonder theserverside made such a blunder.
I would encourage readers to read the content of the blog directly; there are a number of details that are different from the summary posted at the beginning of this thread (among others, there is no reference to XML-RPC in that blog)...
I added JAX-WS to the Javapedia: