Choice of Web Service interaction between Java and. NET

Speaking. for Web service interaction between. NET and Java, the common choice is SOAP over HTTP. ,.. NET is the only way to directly interact with Java Web Servcies.

Recently, two new options are available: WebSphere MQ (WMQ) and ActiveMQ, which can be used to create interactive Web Services between Java and. NET. Moreover, the reliable message system of. NET has been extended. Therefore, for MSMQ, both WMQ and Active MQ can be used as the reliable transmitter of. NET Web Services.

The WMQ solution is based on the Custom Channel (Custom Channel) of the ibm wmq for Windows Communication Foundation in IBM AlphaWorks. Its latest version was released in March 14. This product allows WMQ to be used as a custom channel in the Windows Communication Foundation (WCF) Framework (provided with. NET Framework 3). It works in the same way as Microsoft's built-in channel.

Messages are formatted to meet the SOAP over JMS implementation of WMQ v6.0, allowing applications to communicate with services running on WCF, it can also communicate with services running on the basis of WebSphere SOAP over JMS service, including WebSphere Application Server and CICS.

The current implementation focuses on concept verification to help you better understand the needs of products in this field (that is, it is not suitable for use in the product environment ), how to productize this implementation plan has not yet been finalized.

The custom channel is built through the extensible framework of the Windows Communication Foundation, which allows you to integrate and use a file system similar to the built-in file system provided by Microsoft. A Service-type application can use a new custom channel through configuration. As long as the client application is generated through a standard tool such as Microsoft Service Metadata utility Tool(Svcutil.exe), they can run normally. The metadata Description of a Service can be directly published by a running Service (which can be exposed through an additional HTTP endpoint) or Web Service Description Language (WSDL ).

The current implementation version supports core message functions, which have the following restrictions:

For a service instance, only one client can use the two-way channel mode;

Two-way channel is an extension of the SOAP/JMS implementation provided by WebSphere MQ v6. It can only be used for communication between the WCF Service and its client;

Only core message functions are supported (for example, advanced features such as transaction and security are not supported)

The SOAP/JMS service running in the SOAP/JMS environment of the existing WMQ v6 can only perform one-way operations;

The SOAP/JMS service running in the SOAP/JMS environment of the CICS or WebSphere Application Server does not allow mixed use of one-way operations and request/reply operations in a single contract, separate contracts must be created for each channel form.

The Active MQ solution is based on the JMS (written in Java) and plug-in Protocol features provided by Axis (.. NET). Therefore, it is not true.. NET custom channel packaging, which requires more custom programming.

These two solutions are not completely productized, but they provide a good experimental basis to select the appropriate Web Services interactive transmitter.