Forums Register Login

Portable remote object

+Pie Number of slices to send: Send
Hi all,
Why do we need to use Portable RemoteObject ?
I read that the ejb supports RMI over IIOP and RMI over IIOP is CORBA + JAVA standard. Why is EJB using IIOP ?
Thanks in advance
Hari
+Pie Number of slices to send: Send
We need PortableRemoteObject because some languages do not allow casting and to support this IIOP only allows stubs to implement a single interface. Since Context.lookup() returns an Object, the stub will only implement methods from Object.
PortableRemoteObject gives us a way to cast a general Object to a more specific type, in a protocol independent manner. Thus it will work with RMI-IIOP, T3, RMI, etc...
J2EE uses RMI-IIOP to allow interoperability with existing Corba systems. IIOP is also a more widely recognized protocol than RMI, hence it is more likely to be allowed thru firewalls. It also allows more interoperability between J2EE vendors. Before RMI-IIOP most vendors had proprietary RMI protocols optimized for their server.
when your children are suffering from your punishment, tell your them it will help them write good poetry when they are older. Like this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 1027 times.
Similar Threads
RMI-IIOP queries
rmi/ejb
Implementations with CORBA
Ejb Protocol
If java application talks to EJB tier directly, how to implement SSL?
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 28, 2024 23:39:14.