In Part 2 of this article, we demonstrate interoperability for document-driven web services with Microsoft .NET (C#) using strategies discussed in Part 1.
Tutorial Details:
In a previous article, we explored different patterns and strategies that can be used to build document-driven web services using J2EE technologies, along with their advantages and disadvantages. An important part of developing a document-driven web service is describing it efficiently. So, we also looked at best practices from a WSDL design perspective; namely how to go about separating the data types, and the abstract, concrete parts of the WSDL. We also covered some of the strategies and the considerations that developers should keep in mind when implementing web service endpoints that process the web service messages asynchronously.
The .NET platform is a development framework that provides a new way to create Microsoft Windows-based applications and web services. Within .NET, a few different product groups can be identified. These include the development tools (Visual Studio.NET, the .NET framework) and new programming languages like C#, VB.NET , their class libraries and the Common Language Runtime (CLR); the server products (BizTalk Server, IIS) and services (Hailstorm, Passport.NET). More details about .NET can be found at the Microsoft website.The C# language is surprisingly similar to Java in terms of types, statements, expressions,exceptions and language constructs.
Read
Tutorial at: Click here to view the tutorial
Rate Tutorial: Interoperability with Patterns and Strategies for Document-Based Web Services
View Tutorial: Interoperability with Patterns and Strategies for Document-Based Web Services
Related
Tutorials:
|
RMI over IIOP -
JavaWorld
December 1999