background image

SOAP Transport Protocol

<< Web Services Support | Packaging Applications >>
<< Web Services Support | Packaging Applications >>

SOAP Transport Protocol

SOAP Transport Protocol
Client requests and web service responses are transmitted as Simple Object Access Protocol
(SOAP) messages over HTTP to enable a completely interoperable exchange between clients
and web services, all running on different platforms and at various locations on the Internet.
HTTP is a familiar request-and response standard for sending messages over the Internet, and
SOAP is an XML-based protocol that follows the HTTP request-and-response model.
The SOAP portion of a transported message handles the following:
Defines an XML-based envelope to describe what is in the message and how to process the
message
Includes XML-based encoding rules to express instances of application-defined data types
within the message
Defines an XML-based convention for representing the request to the remote service and
the resulting response
WSDL Standard Format
The Web Services Description Language (WSDL) is a standardized XML format for describing
network services. The description includes the name of the service, the location of the service,
and ways to communicate with the service. WSDL service descriptions can be stored in UDDI
registries or published on the web (or both). The Sun Java System Application Server Platform
Edition 8 provides a tool for generating the WSDL specification of a web service that uses
remote procedure calls to communicate with clients.
UDDI and ebXML Standard Formats
Other XML-based standards, such as Universal Description, Discovery and Integration (UDDI)
and ebXML, make it possible for businesses to publish information on the Internet about their
products and web services, where the information can be readily and globally accessed by
clients who want to do business.
Java EE Application Assembly and Deployment
A Java EE application is packaged into one or more standard units for deployment to any Java
EE platform-compliant system. Each unit contains:
A functional component or components (such as an enterprise bean, JSP page, servlet, or
applet)
An optional deployment descriptor that describes its content
Java EE Application Assembly and Deployment
The Java EE 5 Tutorial · September 2007
52