J2EE/.NET interoperability at last...really!
As reported this week by eWeek, Borland releases Janeva, a J2EE and .NET interoperability and connectivity tool. According to Boz Elloy, Borland's vice president and general manager of enterprise solutions: "Janeva enables .NET clients and servers to connect with J2EE and CORBA back ends using [Internet Inter-ORB Protocol] as the transport mechanism."
Janeva (sounds like Geneva with J for Java) aims to be the neutral bridge between Java and .NET, and will be bundled and shipped with Borland's new C#Builder, an IDE for the .NET framework. This kind of interoperability is crucial for developers these days given the consolidation of companies further increasing the number of heterogeneous development environments. Of course, Web services naturally lend itself to interoperability; however, the level of interoperability provided is limited. There is a need for more powerful, server-side logic-tier interoperability using EJB, COM, and CCM, for example. Janeva is one tool that should accomplish this.
Janeva is one example why Borland has, and will survive. Analysts, editors, and the public wonder if Borland can compete with Microsoft in the Windows developer tools market. Borland isn't competing. They are in their own market. They have the market leading Java IDE in JBuilder. Now, with Janeva and C#Builder, they have provided an interoperable .NET solution for its large base of Java developers who need to work in .NET environments. Long-term, they will grab a larger share of Windows and .NET developers from Microsoft who need to work in a Java environment. Java is still the server-side programming language in the server-side market. Given this, Borland is taking the lead in the programming language interoperability market.
Given the importance on this kind of interoperability, why isn’t there more programming solutions, tools, books, and more on the subject? Of course, Microsoft and Sun have not really provided much on the subject in the form of standard specifications, either.
Comments on this weblog
Return to weblogs.oreilly.com.