Talk:Java Remote Method Protocol

From Wikipedia, the free encyclopedia

You have new messages (last change).

Some raw data:

I could not find references to support these ideas but in brief:

JRMP is the original "RMI protocol" and is often referred to as just "RMI" (lumping the protocol and interface/api in one)

IIOP was added later in part to drive the adoption of J2EE, however, CORBA has increasingly declined in importance with the rise of both Java and WebServices. Thus IIOP's importance has declined and is primarily used for legacy integration (WS is used in new systems where IIOP was intended for use).

Appserver vendors came up with their own protocols for Java-Java invocation such as RMI/IIOP has its disadvantages including making stub generation more laborious. In JBoss for instance a "generic invoker" stub is used for RMI/JRMP and RMI/JBossRemoting but with JBossIIOP stubs must be downloaded for each class: http://www.jboss.org/developers/projects/jboss/IIOP. Since this generic invoker design is "en vogue" with other appservers including Geronimo/WebSphereCE it is likely to continue to be a problem.

BEA Weblogic has T3, a proprietary protocol for their appserver. It claims to be just faster. JBoss has JBoss Remoting for speed mainly secondly it supports the same dynamic invoker design that JRMP does.

WebSphere defaults to IIOP JONAS to JRMP

Retrieved from "http://en.wikipedia.org../../../j/a/v/Talk%7EJava_Remote_Method_Protocol_e8d8.html"