How JNBridgePro works

Figure 1: Eclipse
Click to enlarge

Figure 2: Visual Studio
Click to enlarge

Figure 3: Standalone GUI
Click to enlarge

Figure 4: JNBridgePro Architecture
Click to enlarge

JNBridgePro creates the interoperability bridge by generating a set of proxies that expose the classes' APIs and manage the communications between the .NET and Java classes. You can explore Java or .NET classes with the easy-to-use proxy generation plug-ins in Eclipse (Figure 1), Visual Studio (Figure 2), or the standalone GUI (Figure 3) and determine which classes should have their functionality exposed. JNBridgePro automatically generates the proxies, and will optionally find and expose all the necessary supporting classes.

Once the proxies are generated, and you've added them to your current project, you can access the underlying Java classes from .NET (or .NET classes from Java). When deployed, the .NET classes communicate with the Java classes via your previously generated proxy classes, or vice versa. The .NET code runs on a .NET CLR (Common Language Runtime), and the Java code runs on any conformant JVM.

JNBridgePro's communications architecture (Figure 4) enables the construction of distributed systems with the choice of three communication channels: a fast in-process shared-memory channel, a TCP/Binary protocol based on .NET remoting or an HTTP/SOAP channel. JNBridgePro provides support for J2SE or J2EE and all of the leading J2EE application servers.

Check out the JNBridgePro Technical Overview white paper for more.

Interested in cross-platform transactions? See the description of .NET-to-Java and Java-to-.NET Cross-platform Transactions with 2-Phase Commit.