Developing distributed applications in either J2EE or .NET
Conversely, .NET offers developers multilanguage interoperability. A .NET application can run on any platform that has the .NET Framework on it. This is similar to a JVM, where Java bytecode can run on any platform where a copy of the JVM exists. However, currently only the Windows platforms have the Framework on them.
Enter third-party vendors. JNBridge LLC and Intrinsyc Software are two major vendors of cross-platform technologies for J2EE and .NET. Both have recognized the predicament developers face when attempting to make their choice between J2EE and .NET technologies, and they offer interoperability solutions that share much in common:
Support for enterprise application servers, including WebSphere, BEA WebLogic, Oracle9 i , Borland Enterprise Server, and JBoss
Support for HTTP and TCP/IP protocols
Support for SOAP
Support for binary messages
Invocation of methods on Java objects from the CLR
Invocation of methods on CLR objects from Java
Support for passing Java/CLR objects by reference and by value as parameters/return values
Marshaling objects by value or by reference
It is no longer necessary for developers to make a critical choice. JNBridge LLC’s product, JNBridgePro, and Intrinsyc’s Ja.NET bridge the gap between Java and .NET.
JNBridge’s cross-platform technology is available in two versions: SE (Standard Edition) and EE (Enterprise Edition). The Enterprise Edition is covered in this chapter. But before going into the details of JNBridgePro, we’ll take a brief look at Intrinsyc’s solutions.
Ja.NET makes it possible to write
Ja.NET provides a tool called GenJava to generate a Java proxy for .NET components. For example, access to an Internet Information Server (IIS) component from Java is easy. The Janetor tool configures the Ja.NET runtime. Then, Java clients can use the proxies to access a remote CLR component as though it were a local Java component. The tool can also generate a .NET component
Intrinsyc Software has another interop tool called J-Integra. It is a COM-Java tool employed for accessing ActiveX components as though they are Java objects. Conversely, accessing Java objects as though they are Microsoft .NET components is allowed. J-Integra works seamlessly with any Java Virtual Machine on any platform and requires no native code. Additionally, J-Integra speaks native DCOM and is layered over Remote Procedure Calls. J-Integra requires no JVM or additional software
Ja.Net and J-Integra technologies are worth pursuing. You can