Still waiting for true interoperability

by Amir Shevat

One of the big things presented in JavaOne was .NET-Java interoperability. The notion of language interoperability can be understood and implemented in several different ways.


Stephen Bloch
2006-05-28 15:02:11
You can compile almost every popular language into MSIL code, you can run complex Java application with IKVM. In addition, the Mainsoft company you've mentioned above has much more to propose than a "simple demo" - check their dev site

2006-05-28 22:51:45
I agree with you. You forgot to mention IIOP: there are mature open source projects that implement interoperability between java and dotNET using IIOP. It has the benefit to be well documented and works faster on the same machine, but works well over TCP/IP too. And the two VM (java and dotNET) are on different processes, so each one has its own responabilities and if one crashes, the other keeps on working. And it works (don't know how well) with other CORBA implementations, written in C++.
I think good things shouldn't be thrown away: CORBA was over-engineered for the (mass) needs of the time, but now fits well all these interoperability and distributed (object)systems issues.
The good moment for webservices is due to its beeing HTTP-transport-based, but these is its defect too: security. Bad written webservices expose your code to the word.
when business-people will recognize this, perhaps somebody will open IIOP ports and use CORBA security through firewalls.
Too optimistic ? Bye