Jesus Rodriguez's WebLog

My last article explains how to develop content-based-routing Web Services in WSE, Indigo and J2EE. The article also covers the WS-* specifications that are used in each case. Read More....

JNBridgePro  adds some new features in the new version. T most remarkable of all is the shared-memory communication channel.

JNBridgePro now includes a shared-memory communication channel. The new shared-memory channel uses an in-process communication path and thus eliminates the overhead of sockets and inter-process communication. In the architectural scenarios where the shared-memory communication channel can be used, it provides an even faster interoperability path between Java and .NET. JNBridgePro still provides speed-optimized TCP/Binary and HTTP/SOAP communication paths to be used when a socket-based communication mechanism is necessary.

IBM announces another technology for COM-Java interoperability.

Development Tool for Java-COM Bridge is a tool for developing and enabling tight communication between Java^TM- and COM-based applications. An application running on Microsoft Windows® systems is typically constructed as a set of interconnecting components entirely based on Microsoft Component Object Model (COM) technology, or on Java technology. There is not a simple, direct way to connect a COM-based component with a Java-based component.

In the past I develop so really cool examples using BEA JCOM, the fact is that java and ms developers have a lot of option to think in interoperability.

Steve Maine has been developed a custom SMTP transport for WSE. We can now develop Web Service applications that work in a disconnected mode. Have fun.

OTP systems has announced the release of  JTux and DotTux two software packages that integrates Tuxedo with Java and .NET.

BEA TUXEDO is one of the most powerful platforms to develop distributed transaction and message-based applications. Now we can write TUXEDO clients and servers in Java and C# using JTux and DotTux.

Enterprise Service Bus (ESB) is a vital concept in the Service Oriented Architecture (SOA) vision of the majority of Web Service technology providers. This nice article explain some of the main aspects of ESB.

Ingo Rammer post a nice reflection about the missing aspects of System.Messaging.

Steve Vinoski exposes his opinion about expose object as services. This is a recurrent theme in the majority of Web Service technology consumers.

Another example of alternative XML technologies to optimize the size of XML documents can be founded here.

Great work!. I think that this type of technologies are very useful. However XML is XML and, is not the case, one of the most remarkable capabilities is readability. All technology providers can be very careful with this aspect.

Several companies had expressed the intention of arrive to some kind of convergence in the area of Web Service Referencing and Addressing.

In an Open Letter   to the W3C, 11 companies ask for "an open and honest" debate to see if there is a way to charter a new Working Group with a purpose "to define extensible and reusable mechanisms to reference Web Services, to allow such Web service references to be passed in messages, and to support WSDL Messsage Exchange Patterns". The objective is to bring convergence in the area of Web Service Referencing and Addressing as there are two major specifications, WS-Addressing and WS-MessageDelivery.

Addressing is a neural aspect in the Web Services world. WS-Addressing have been adopted by a series of technology providers and WS-MessageDelivery is a very complete specification. I think that unifying concepts between the two specifications is a key aspect for the Web Service interoperability .