JavaSoft to solve RMI's interoperability problem

Sun's JavaSoft division has responded to partner pressure and announced that it will integrate its Remote Method Invocation (RMI) protocol with the Object Management Group's Common Object Request Broker Architecture (CORBA) specification. Everybody is pleased.

Sun's JavaSoft division has responded to partner pressure and announced that it will integrate its Remote Method Invocation (RMI) protocol with the Object Management Group's Common Object Request Broker Architecture (CORBA) specification.

RMI enables Java objects to talk across a network doing roughly the same job as CORBA's Internet Inter-ORB Protocol (IIOP) or Microsoft Corp.'s Distributed Computing Environment (DCE).

Recently JavaSoft partners such as IBM, Netscape Communications Corp. and Oracle Corp. have attempted to pressure JavaSoft into scrapping RMI because it was confusing the market.

Following discussions with the Object Management Group this week, JavaSoft decided to enable RMI requests to travel over CORBA's Internet InterOrb Protocol (IIOP), according to Jim Mitchell, JavaSoft's, vice president of technology and architecture.

The company has made three decisions concerning RMI. Firstly, RMI will be included in the Java Interface Definition Language (IDL) in the next version of the Java Development Kit. Secondly, JavaSoft will, with the help of the OMG, build in all RMI functionality into IIOP. Thirdly, JavaSoft will not only continue to support RMI but push it as its primary method of promoting distributed computing, Mitchell said in a telephone conference today.

Until now, RMI has used its own transport protocol which has been one of the features of the protocol that has prompted criticisms the technology is not compatible with CORBA.

"The RMI over IIOP is a plan to save face for Sun," says Don DePalma, a senior analyst at Forrester Research. "It's implicitly admitting that a highly optimised, proprietary object technology won't win it any points with the open CORBA crowd that it's taken up with. But if Sun has to do any additional engineering to make this happen, that effort will steal resources from the pure IIOP work they are undertaking."

In addition to allowing RMI requests to travel of CORBA's IIOP, in the long run JavaSoft wants programmers to write to the Enterprise JavaBeans Application Programming Interface, a higher level of programming eliminating the need to worry about transport protocols.

"We are trying to add another layer of abstraction," says Sharada Achanta, JavaSoft's product line manager for enterprise Java. "We believe that Java programmers should not have to worry about what are basically plumping issues of RMI and IIOP."

Users are welcoming the move.

"This will be a real step forward," says Tracy Ikard, senior product manager with Scientech Inc., an Idaho-based systems Integrator. "Until now the only way we could guarantee interoperability between applications has been to employ one of the Orb vendors such as Iona or Visigenic to provide this integration for us."

"This is exactly what we in the development community want and needed to hear," says Jim Kleckner, chief technical officer of Cats Software, a California-based risk management software vendor. "Who knows how many people might head down the RMI path only to find that it becomes a dead end? Very costly when that happens."

Independent CORBA vendors such as the Dublin, Ireland-based Iona Technologies have also welcomed the announcement .

"It's very good news that JavaSoft is supporting IIOP as a means for application integration over the Internet," says Colin Newman, vice president of marketing at Iona. "It's just as important that we all support IIOP so that our applications can interoperate as it was for the networking vendors to support TCP/IP.

Seven vendors have come out in support of JavaSoft's decision to extend RMI to CORBA, including Oracle, IBM, Sybase, Informix, Novell, Netscape, and Sun itself.

Join the newsletter!

Error: Please check your email address.
Show Comments
[]