<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- /*******************************************************************************
 * Copyright (c) 2000, 2005 IBM Corporation and others.
 * All rights reserved. This program and the accompanying materials
 * are made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at
 * http://www.eclipse.org/legal/epl-v10.html
 * 
 * Contributors:
 *     IBM Corporation - initial API and implementation
 *******************************************************************************/ -->
<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
<title>JAX-RPC</title>
</head>
<body id="cjaxrpc"><a name="cjaxrpc"><!-- --></a>

<h1 class="topictitle1">JAX-RPC</h1>
<div><p>JAX-RPC stands for Java™ API for XML-based RPC, also known as
JSR 101. It is a specification that describes Java Application Programming Interfaces
(APIs) and conventions for building Web services and Web service clients that
use remote procedure calls (RPC) and XML. It standardizes the Java to
WSDL and WSDL to Java mappings, and provides the core APIs for developing
Web services and Web service clients on the Java platform. Often used in a distributed
client/server model, an RPC mechanism enables clients to execute procedures
on other systems.</p>
<p>The current release of JAX-RPC requires the support of SOAP over HTTP for
interoperability purposes. The SOAP specification defines message structure,
encoding rules, and conventions for exchanging information in the RPC programming
model. These calls and responses are transmitted as SOAP messages over HTTP.
In this release, JAX-RPC supports SOAP 1.1 and HTTP 1.1. For more information
on SOAP, refer to <a href="csoap.html">Simple Object Access Protocol (SOAP)</a>.</p>
<p>Although the underlying run-time mechanisms (for example, Java to
WSDL serialization, WSDL to Java deserialization, protocol and transport)
are very complex, the API hides this complexity from the application developer.
On the server side, the developer can provide a Service Endpoint Interface
(SEI); alternately an SEI can be created using the Web services wizrds. An
SEI is an interface written in the Java programming language that specifies
the remote procedures of a Web service. The developer also provides the implementation
of a Web service, in the form of one or more Java classes that implement methods of the
same signature as those on the SEI. Client programs are also easy to code.
A client creates a proxy, a local object representing the service implementation
and the SEI, and then simply invokes methods on the proxy.</p>
<p>JAX-RPC is highly interoperable: a JAX-RPC client can access a Web service
that is not running on the Java platform and vice versa. This flexibility
is possible because JAX-RPC uses SOAP over HTTP, and the Web Service Description
Language (WSDL). JAX-RPC was designed to support WS-I.</p>
<p>For more information on JAX-RPC, refer to the  <a href="http://www.jcp.org/en/jsr/detail?id=101" target="_blank">official JSR 101 specifications</a>.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div>
</div>

<div class="linklist"><strong>Related Concepts</strong><br />

<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div>
<div><a href="cwsinwsa.html">Tools for Web services development</a></div>
<div><a href="cjsr109.html" title="JSR 109 and JSR 921 (Implementing Enterprise Web Services) define the programming model and run-time architecture to deploy and look up Web services in the J2EE environment; more specifically, in the Web, EJB, and Client Application containers. One of its main goals is to ensure vendors' implementations interoperate.">JSR 109 and JSR 921- Implementing Enterprise Web services</a></div></div>

<div class="linklist"><strong>Related Tasks</strong><br />

<div><a href="../tasks/toverws.html"> Developing
Web services</a></div></div>
</div>
</body>
</html>