How to connect Java end with .NET interface

I have a bunch of Java code that was written using the Hibernate framework, originally designed to work with a JSP interface. However, the interface requirements have changed and we decided that the desktop client (which will be written in .NET) is a better fit for our users.

I really don't want to lose the code that has already been written - can anyone suggest a good set of tools for writing a document-based web services interface that we can access from .NET?

Thank,

Jim

0


source to share


4 answers


We develop an application with the exact architecture that you describe for a financial application. We looked at several different options and finally landed on CSV compression over HTTP.

CSV was chosen because the vast majority of the data was going to be displayed in a front panel grid, we had very large result sets> 250k rows on a regular basis, and it compresses very efficiently.

We also looked at the usage:



  • ICE, but dropped it due to licensing costs and the need to reinvent it multiple times.
  • Google protocol buffer via servlets but dropped this due to lack of C # support (as of last fall).
  • Compressed XML using WOX, but dropped it due to blocking a small thesis project to maintain and XML being too verbose

The industry also supports several different options:

  • SOAP, but it has its own well-documented problems.
  • IIOP, J-Integra has a product called Espresso that will allow you to do RMI from the front.
0


source


If you really want a document-based service interface (not an RPC-style web service architecture), your best bet is to create a SOAP-based web service interface.

A quick look at the Java site reveals that the Metro stack can help a little:



A Brief Introduction to Java Web Services

+1


source


I personally would use a lightweight RPC protocol, be it XML-RPC or homebrew. SOAP, IMO, is too fat and not as interoperable as intended. The simpler the better.

0


source


We have a fairly large application using Java RMI Server and IIOP.NET for communication. We used IIOP.NET with Sun RMI and Bea Weblogic (now Oracle) without major issues.

0


source







All Articles