Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Save to My Library
Look up keyword or section
Like this
0 of .
Results for:
No results containing your search query
P. 1
Web Services

Web Services

Ratings: (0)|Views: 548|Likes:
Published by satyanarayana

More info:

Published by: satyanarayana on Dec 29, 2008
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





Web services
documents contain the information being exchanged between two parties. It isused to organize documents and business data. XML files can be stored ortransmitted between two applications on a network.
provides a packaging and routing standard for exchanging XML documentsover a network. A SOAP message is just an XML document. SOAP is speciallydesigned, however, to contain and transmit other XML documents as well asinformation related to routing, processing, security, transactions, and other qualitiesof service.
allows an organization to describe the types of XML documents and SOAPmessages that must be used to interact with their Web services. 
allows organizations to register their Web services in a uniform mannerwithin a common directory, so clients can locate their Web services and learn howto access them.
A SOAP Message That Contains Address Information
<?xml version="1.0" encoding="UTF-8"?><soap:Envelopexmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"xmlns:addr="http://www.Monson-Haefel.com/jwsbook/ADDR" ><soap:Body><addr:address><addr:name>Amazon.com</addr:name><addr:street>1516 2nd Ave</addr:street><addr:city>Seattle</addr:city><addr:state>WA</addr:state><addr:zip>90952</addr:zip></addr:address></soap:Body></soap:Envelope>SOAP takes advantage of advanced XML features like XML namespaces(similar to Java package names) and XML schemas (used to typedata)
SOAP messages serve as a network envelope for exchanging XMLdocuments and data.
There are actually two versions of SOAP today, versions 1.1 and1.2.
SOAPMessages with Attachments 
(SwA):SwA defines a messageformat for attaching binary data (images, sound files,documents,and so on) to SOAP messages.
(Web Services Description Language) is a standard fordescribing the structure of the XML data exchanged between twosystems using SOAP.When you create a new Web service, you can also create a WSDLdocument that describes the type of data you're exchanging
There are two versions of WSDL today, versions 1.1 and 1.2.Although WSDL provides an excellent format for describing thetypes of SOAP messages used by a Web service, it provides noguidance on where to store the WSDL documents or how to findthem. In other words, WSDL doesn't describe where the WSDLdocuments should be kept so that others can find them easily anduse them to communicate with your Web services
UDDI (Universal Description, Discovery, and Integration)
defines a standard set of Webservice operations (methods) that are used to store and look up information about other Webservice applications.In other words, UDDI defines a standard SOAP-based interface for a Web services registry.You can use a UDDI registry to find a particular type of Web service, or to find out about theWeb services hosted by a specific organization.A UDDI registry is often referred to as a "
Yellow Pages" for Web services.When you look up information about a Web service in a UDDI registry, you can narrow your search using various categories (technologies used, business types, industry, and so on).Each entry in a UDDI registry provides information on where the Web service is located and howto communicate with it.
The UDDI registry also provides information about the organizationthat hosts a particular Web service.UDDI can also store data about other types of services, such as a Web site or a phone service.There are three versions of UDDI at this time, versions 1.0, 2.0, and 3.0.
J2EE Web Service APIs
:JAX-RPC: Java API for XML-based Remote Procedure CallsSAAJ:JAXR:JAXP:These are the APIs you will need to understand if you want to implement Web serviceapplications using the J2EE platform.Perhaps the most important Web service API is JAX-RPC, which is used to implement J2EEWeb service clients and endpoints (services)JAX-RPC is divided into two parts:1) a set of client-side APIs2) A set of server-side components, called endpoints.The client-side APIs allow you to communicate with Web service endpoints hosted on someother platform.For example, you can use one of the client-side APIs to send SOAP messages to a VB.NET or an Apache Axis Web service. The client-side APIs can be used from standalone Javaapplications or from J2EE components like servlets, JSPs, or EJBs. There are three client-side APIs:1)generated stub(MOSTLY USED)2) dynamic proxy3)DII (Dynamic Invocation Interface).The
generated stub
is the one you will use the most, and its semantics closely resemble those of Java RMI.The
dynamic proxy API
also follows many of the Java RMI semantics, but is used less often.The
is a very low-level API used primarily by vendor tools, but can also be employed byWeb services developers if necessary.The server-side components include the JAX-RPC service endpoint (JSE) and the EJB endpoint.The JSE component is actually a type of servlet that has been adapted for use as a Web servicescomponent. It's very easy to implement, yet it has access to the full array of services andinterfaces common to servlets.

Activity (14)

You've already reviewed this. Edit your review.
1 hundred reads
athirai liked this
kinnu999 liked this
Saud Alharbi liked this
Vipin Jain liked this
altafvasi9380 liked this
nur syahidatul liked this
vijaykumar015 liked this
msnvasu1561 liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->