DotNetJ allows .NET applications to access ObjectWeb's JOnAS hosted J2EE applications
DotNetJ can be used in conjunction with ObjectWeb's strong Java application server JOnAS to build rich Windows applications linked to existing J2EE applications.
As enterprise information systems become more and more heterogeneous today, many attention is paid to web services as the solution to interoperability issues. Although web services come as the universal glue between platforms, its semantics reduces the relationships that could exist between objects. In other words, a .NET client application, by connecting itself to a web service, cannot access all the objects contained in the target J2EE application, it is instead restricted to the functions exposed by the web service.
Web services applied to .NET to J2EE interoperability stand as an intermediate layer that filters the interactions between the EJBs and the .NET client. In this scenari, web services are a bottleneck.
DotNetJ, combined to JOnAS, features a full EJB access to .NET clients, remote objects are really used as if they were local. As shown in the figure below, the VB.NET client connects directly to the JOnAS server and thus is able to leverage the power of the hosted J2EE applications.
Moreover, the DotNetJ-JOnAS communication framework offers much more performances and liability than the SOAP alternative, due to its fast binary protocol and its support for transactions.
How it works
JOnAS provides an internal interface for plugging protocol providers to it's EJB container. Since DotNetJ's proprietary binary protocol supports all the features required to distribute EJBs, it can come and add .NET support to JOnAS.
Installing DotNetJ in JOnAS can be achieved by simply adding a property in the configuration file, without compromising the protocols already installed.
For more information : ObjectWeb consortium, JOnAS home.
© Copyright 2003 Romain Laboisse. All rights reserved.