Most Read Latest News Blog Resources
Digg!  Digg
Reddit  Reddit


            iphoneapp GET THE APP!

Many Ways to Skin .NET and Java Integration


Vendors are taking three basic approaches to bridging the two technologies



July 15, 2004 —  (Page 1 of 3)
It used to be that .NET and J2EE were Web services islands, connected only by communication between finished applications, but now vendors have begun shipping tools that bridge the two architectures.

Using the various kinds of tools now available, organizations can build individual applications that take advantage of aspects of both .NET and J2EE.

Companies have taken three basic approaches to trying to get the two technologies to communicate. They involve translation, sharing code, and traditional integration middleware.

TRANSLATION, PLEASE
Bridging software such as CodeMesh Inc.'s JuggerNET, Intrinsyc Software International Inc.'s Ja.Net, and JNBridge LLC's JNBridge Pro use the translation approach.

This kind of software is faster than using Web services for integration because Web services must transmit XML files, which are typically larger than executable files, and they require the extra step of translating XML on both ends, said Wayne Citrin, CTO of JNBridge.

"The conversion takes time, plus the XML is bigger than a binary-encoded message," he said. "If the message is bigger, the more time it takes across the wire."

The software is most often used in situations where an organization needs to connect .NET clients with Java servlets, although JNBridge and Ja.NET work bidirectionally. They work by having a series of .NET proxy classes that stand in for Java classes, and include the software vendors' proprietary software for managing the communication between the two systems. JNBridge Pro and Ja.NET include Java proxies for mimicking .NET instructions.

Borland Software Corp.'s Janeva has a twist on the translation theme.

"[Bridging technology is] like having somebody translate," said Vince Taisipic, senior product manager at Borland. "Janeva goes in and makes .NET applications trilingual, if you will."

Instead of providing a proxy that translates on-the-fly between the two classes, Janeva inserts code that gets compiled with the application, Taisipic said.

"Janeva is inherently part of the .NET application," he said. "Janeva is compiled into the application itself. When you deploy your application, Janeva is part of it." He described this as more direct than the bridge approach and added that in many cases, using a bridge requires .NET programmers to understand something about J2EE or CORBA.


Pages 1 2 3 


Share this link: http://www.sdtimes.com/link/28022
 

Add comment


Name*
Email*  
Country     


  • Comment
  • Preview
Loading



 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 
Download Current Issue
ISSUE 8/1/2010 PDF

Need Back Issues?
DOWNLOAD HERE

Receive the print Edition?


 
blogs tab
Like Ruby n' Rails
Programming languages and Web frameworks go together like peas n carrots. Or Ruby n' Rails.
07/30/2010 04:36 PM EST

Adobe buys a Web-based IDE
Adobe looks to buy a rapid and agile Web development environment.
07/28/2010 03:49 PM EST

OpenStack opens up
OpenStack looks to be an intriguing new idea for running clouds.
07/28/2010 01:56 PM EST

 

Events calendar tab
8/1/2010 to 8/5/2010
Boston
SHARE

8/2/2010 to 8/6/2010
Redmond, Wash.
1105 Media

8/9/2010 to 8/13/2010
Orlando
Agile Alliance

8/23/2010 to 8/26/2010
San Jose
S&S Media

8/30/2010 to 9/2/2010
San Francisco
VMware