Java201.com

• Web Services programming tips and tricks, Part 4: Bring J2EE and .NET together in a business process using BPEL and WebSphere Business Integration Server Foundation by Wangming Ye   - [Clicks: 100]
  Investigate a typical business integration scenario between J2EE (Java 2 Enterprise Environment) and Microsoft .NET and learn how to build and run a BPEL (Business Process Execution Language) business process on IBM WebSphere Business Integration Server Foundation. In the first three parts of this series about improving interoperability between J2EE technology and .NET, Wangming Ye analyzed the common challenges facing the Web services integration between J2EE and .NET, and offered best practices. This tip focuses on the delicate design of XML schemas that Web services programmers often overlook. The objective is to show you how to avert common Web service interoperability challenges between .NET and J2EE, such as nested complex-type arrays, date and time values, and namespace issues, through a top-down approach (WSDL (Web Services Description Language) implementations).
  [Includes sample code]
  http://www-128.ibm.com/developerworks/webservices/library/ws-tip-j2eenet4/ - May, 2005
• J2EE and .NET: Presentation Tier Interoperability by Binildas Christudas   - [Clicks: 136]
  Many enterprise projects use .NET based technology on the client side, where richness and performance are paramount considerations. This is then teamed up with a proven, stable, mature platform for server based enterprise applications, J2EE. While many enterprise projects have realized the power of this dynamite combination, several questions related to the interoperability considerations of using .NET with J2EE have gone unanswered. In this article, Binil Christudas attempts to shed light on this important, yet sparsely documented, area of interoperability considerations and some of the solutions available to work hassle-free with .NET and J2EE . The article converges at a point, and rightly so, to propose Web Services as a technology for attaining client side interoperability, and in that attempt addresses two important approaches: Top-Down and Bottom-Up. As proof of the proposed technology, practical demonstration of the two approaches, and the successful implementation of a solution, the author showcases a sample architecture based on BEA Weblogic Server and .NET C# client. Cruise along and pick up some nuggets for your next project that uses this potent combination.
  http://www.jaxmagazine.com/itr/online_artikel/psecom,id,676,nodeid,147.html - Mar, 2005
• Web services programming tips and tricks: Improve interoperability between J2EE technology and .NET, Part 3 by Wangming Ye   - [Clicks: 74]
  Explore the source of the common interoperability challenges facing Web services integration across platforms. This third part in a series describes how the different naming conventions between J2EE technology and .NET can cause difficulty in Web services interoperability.
  http://www-106.ibm.com/developerworks/webservices/library/ws-tip-j2eenet3/ - Feb, 2005
• Interoperability With Patterns and Strategies for Document-Based Web Services by Sameer Tyagi   - [Clicks: 54]
  In this article, we examine some of the strategies discussed earlier, and demonstrate interoperability with C#. To run the example code discussed below, you must first build and deploy the web services. Details on how to do that, along with the sample code, including Ant build scripts can be found in the previous part. To execute and build the C# code, you need to install the .NET 1.1 framework and the CLR (and contrary to popular belief you don't actually need to install Visual Studio).
  http://java.sun.com/developer/technicalArticles/xml/jaxrpcpatterns2/index.html - Jan, 2005
• Web services programming tips and tricks: Improve the interoperability between J2EE and .NET, Part 2 by Wangming Ye   - [Clicks: 55]
  Part 2 of this series explores the source of common interoperability challenges facing Web services integration across platforms. Follow along as Wangming Ye analyzes the interop failures resulting from the use of certain data types and ways to overcome them such as collections, arrays, or primitive data types.
  http://www-106.ibm.com/developerworks/webservices/library/ws-tip-j2eenet2.html - Jan, 2005

[Top]