• Post Reply Bookmark Topic Watch Topic
  • New Topic

.NET and J2EE Interoperability  RSS feed

 
Joe Skora
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We are in the process of evaluating whether a J2EE or .NET platform is better for our in house application development. The most likely conclusion is that they are capable of meeting our requirements. That being the case is there a "preferred" J2EE platform for interoperability with .NET or are they all equal in that regard?
Thanks,
Joe Skora
 
Gary Blomquist
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What about using sockets for a low cost java .NET interoperability solution? Are there any cross platform issues i.e. big endian/little endian, etc.? I think sending strings over sockets might work without issues.
 
Byron Estes
Ranch Hand
Posts: 313
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't think you'll run into a issue with the string encoding, but I would urge you NOT to write your own socket based server.
First you'd need to write a mutithreaded server and you'd need to have the caller have knowledge of the server ip and port you're service is listening upon. You need to establish some basic protocol related to message request and response format, not to mention error handling.
Additional issues that would need to be at least considered would need to deal with stuff like security, session state, etc. For instance, what happens the month after you implement it and your boss realizes you're sending clear text over the network? How are you going to secure it without drastically changing what you've done, including the clients that are calling your home grown, non standard server?
Sometimes things that sound easy and cheap in dollars, end up costing more in manpower and headaches when implemented.
It would also be non standard and you'd need to support that with no recourse except to re-write it later when you needed to access it another way.
I'd go with simple RPC webservice using SOAP/IIOP. All the the issues I mentioned would be handled and there are plently of free servers/containers to serve it up.
[ March 26, 2004: Message edited by: Byron Estes ]
 
Byron Estes
Ranch Hand
Posts: 313
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There are plenty of other solutions out there, the web service one is just simple and ubiquitous...
 
David Dossot
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Absolutely!
I am involved in a project where we have nice Word 2003 C# smart documents gracefully talking to EJBs deployed as web services on JBoss 3.2.3 - all this quickly, neatly and easily done.
David Dossot
-----------------
http://dossot.net
 
Nicholas Cheung
Ranch Hand
Posts: 4982
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In fact, Web services is one of the best solutions to cater the communication between 2 systems which are implemented by different languages.
Web services using HTTP, which you do not need to handle how the 2 systems communicate with what protocol (socket, rpc etc). Web services also focus on data, using XML, and thus, the 2 systems only need to know XML, and then converted into the require object format after exchange the data for further process.
I think this is one of the beauty of Web services.
Nick
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!