Network Deployment (Distributed operating systems), v8.0 > Applications > Web services > Web services > JAX-RPC
RMI-IIOP using JAX-RPC
Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP) can be used with JAX-RPC to support non-SOAP bindings.
Java API for XML-based Remote Procedure Call (JAX-RPC) is the Java standard API for invoking web services through remote procedure calls. A transport is used by a programming language to communicate over the Internet. We can use protocols with the transport such as SOAP and RMI. We can use Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP) with JAX-RPC to support non-SOAP bindings.
Use RMI-IIOP with JAX-RPC, enables WebSphere Java clients to invoke enterprise beans using a WSDL file and JAX-RPC instead of using the standard Web Services for Java EE programming model. When a enterprise JavaBeans implementation is used to invoke a web service, multiprotocol JAX-RPC permits the web service invocation path to be optimized for WebSphere Java clients.
To learn more this optimization, read about using enterprise bean bindings to invoke an EJB from a web services client.
Benefits of using the RMI/IIOP protocol instead of a SOAP- based protocol are:
- XML processing is not required to send and receive messages; Java serialization is used instead.
- The client JAX-RPC call can participate in a user transaction, which is not the case when SOAP is used.
JAX-RPC
WSIF Overview
Use WSDL EJB bindings to invoke an EJB from a JAX-RPC Web services client
Concept topic