16.1. The Basics of JAX-RPC
Beneath the surface, JAX-RPC clients and servers are exchanging SOAP messages, each of which contains XML representations of the parameters and return values of the methods being called. But as a JAX-RPC programmer, you only need to think in terms of Java objects; the fact that SOAP is being used underneath is completely transparent. In fact, JAX-RPC is designed to be fully compatible with other underlying transports. At the first release of JAX-RPC, SOAP 1.1 and HTTP are required, but future releases may allow different low-level implementations.
Because of this focus on objects, using JAX-RPC is very similar to using Java RMI; it feels much more familiar to a Java programmer than JAXM does. But some surprises are ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access