Main BLOGGER
Google
WWW THIS BLOG
Monday, March 13, 2006
 
web services deployment in J2EE, .NET

1.      Categorized by dependency on container: container-dependent or container-less standalone web services

2.      Categorized by communication model: RPC and HTTP based web applications and XML messaging based standalone applications

 

 

 

http://java.sun.com/webservices/whatsnew.html

·  Java WSDP 1.4 provides support for multiple Web containers. You can choose to integrate the Java WSDP 1.4 technology components with any of the following:

  • Sun Java System Application Server Platform Edition 8
  • Sun Java System Web Server 6.1
  • Tomcat 5.0 for Java WSDP
  • No Web container initially, then integrate with one of the previously mentioned Web containers or, with script modifications, with your own Web container at a later time

Java WSDP 1.4 adds support for the following profiles, based on draft versions dated April 19, 2004:

  • WS-I Basic Profile 1.1
  • WS-I Attachment Profile 1.0
  • WS-I Simple SOAP Binding Profile 1.0

Java API for XML-based RPC (JAX-RPC) v1.1.2 enables Java developers to develop SOAP-based portable Web services. JAX-RPC technology has support for the Web Services Interoperability Organization (WS-I) Basic Profile 1.1 with Attachments Profile 1.0. WS-I is an organization that aims at developing guidelines and tools to help developers in building interoperable Web services. The Basic Profile enables interoperability for your Web services, and the Attachments Profile compliments the Basic Profile 1.1 by adding support for conveying interoperable SOAP messages with attachments with SOAP messages.

 

J2EE with Web Services, category one

http://www.adtmag.com/article.aspx?id=8268&page=

 

 

J2EE Web services: A marriage of convenience

As specified in the following snippet taken from the J2EE specification, the J2EE platform contains details on the implementation, assembly, deployment and consumption of Web services: “J2EE provides full support for both clients of Web Services as well as Web Service endpoints. Several Java technologies work together to provide support for Web Services. The Java API for XML-based RPC (JAX-RPC) provides support for Web Service calls using the SOAP/HTTP protocol. JAX-RPC defines the mapping between Java classes and XML as used in SOAP RPC calls. The SOAP with Attachments API for Java (SAAJ) provides support for manipulating low-level SOAP messages. The Web Services for J2EE specification fully defines the deployment of Web Service clients and Web Service endpoints in J2EE, as well as the implementation of Web Service endpoints using enterprise beans. The Java API for XML Registries (JAXR) provides client access to XML registry servers.”

The life cycle of J2EE components and Web services is not dissimilar; they almost mimic one another as both have sprung from similar distributed computing ideologies. From modeling a Web service to its creation, binding, deployment, publishing and consumption, a Web service presents no new tenets for understanding, and its inclusion in the J2EE component stack is a logical addition to enable loosely coupled interaction between applications. The combination of J2EE and Web services seems to be a perfect match:

 

 

ASP.NET with Web Services, category one

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnacc2k2/html/odc_webvsnet.asp

 

 

XML Web services provide a way for applications to exchange data and processing capability. Typically, an XML Web service is a dynamic-link library (DLL) that resides on a Web server and whose methods can be called over the Internet. In this scenario, a client application communicates with an XML Web service by sending and receiving SOAP messages over Hypertext Transfer Protocol (HTTP).

In this article, we will demonstrate how to create, deploy, and access an XML Web service using Microsoft® Visual Studio® .NET. First, we'll set up Internet Information Server (IIS) on the Web server hosting the XML Web service.

Note   IIS 4.0 is compatible with Microsoft Windows NT® 4.0 Server. IIS 5.0 is compatible with and installed by default with Windows® 2000 Server.

Then, using Visual Studio .NET, we'll create an ASP.NET Web Service project. Next, we'll add code to the project to implement the XML Web service. Our sample XML Web service will accept the two-digit name of a U.S. state and return information about the state to include the state's full name, its capital, the date the state was admitted to the union, and its order of admittance. We'll then test the XML Web service in Visual Studio .NET. And finally, we'll create a client application using a Microsoft Access 2002 form to access the XML Web service and display the results.

 

 

WSE for Web Services, category two

http://msdn.microsoft.com/webservices/webservices/building/wse/default.aspx?pull=/library/en-us/dnwse/html/wsemessaging.asp

 

The State of XML Messaging Today

Today one might expect to see many Web services, built over a variety of communication protocols and employing many different message exchange patterns. In reality, however, the vast majority of Web services are implemented as a collection of Remote Procedure Calls (RPC) over HTTP. This is primarily because that is the model promoted by most of today's Web service frameworks and toolkits. Such frameworks map the synchronous exchange of SOAP messages, carried in HTTP request and response messages onto the remote invocation of a method, on a class. HTTP was chosen because both client-side and server-side HTTP plumbing are available on every platform. The RPC model was adopted because of its familiarity and relative ease of use—it doesn't scare off developers. The RPC model is limiting, though. There are many other message-exchange possibilities if you are not tied to the predominantly synchronous, request-response model of RPC over HTTP. Also, the RPC approach eschews an XML-oriented view of data in favor of an object-oriented view, and this tends to lead to very tightly-coupled systems. There are real opportunities for building loosely-coupled systems that can evolve over time, if you are prepared to discard RPC and adopt a more XML-oriented view of the world.

It is generally possible to build a Web service that deviates from what the Web service runtime and tools want you to do. Even though the Microsoft ASP.NET .ASMX framework is geared towards implementing RPC-oriented Web services, it would be possible to write a more XML-oriented service by having the WebMethods accept an XmlNode as a parameter. HTTP cannot easily be replaced as the underlying protocol, however, as ASP.NET is centred on HTTP.

 




<< Home

Powered by Blogger

Google
WWW THIS BLOG