On Dec 7, 2006, at 2:43 PM, Gregg Wonderly wrote: > Stefan Tilkov wrote: > > > > > > On Dec 6, 2006, at 8:13 PM, Gervas Douglas wrote: > > > > > "The core tenet of SOA is loose coupling within Web services and > > > without," Kassem said. "In Web services, our [J2EE 1.4] initial > foray > > > was very RPC-centric. That dramatically shifted with JAX-WS > 2.0, it > > > was an important programming model shift. It enables us to > build more > > > loosely coupled Web services that will scale very well for the > Web. > > > [It] was a significant SOA-centric initiative. > > > > Bullshit. JAX-WS is as RPC-centric as the JAX-RPC/JAXM combination. > > Depending on what you transport and how the interface is described, > RPC is > equivalent to messaging. The standing issue for interoperability is > a common, > known wire protocol. Maybe you can elaborate on the rift that you > perceive? >
RPC hides the fact that you're sending a message over a network, and tries (but fails) to create the illusion of a "remote method call". JAX-RPC basically treats the fact that you're sending XML messages over a net as an implementation detail. JAXM didn't, but unfortunately was (semi-officially) retired. JAX-WS is 90% RPC, with a little messaging integrated - but any JAX- WS compliant implementation will have to support all of the RPC madness. Stefan -- Stefan Tilkov, http://www.innoq.com/blog/st/
