This week's book giveaway is in the Kotlin forum.
We're giving away four copies of Kotlin in Action and have Dmitry Jemerov & Svetlana Isakova on-line!
See this thread for details.
Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

PortableRemoteObject.narrow()  RSS feed

 
Prashanti Potukuchi
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Why is PortableRemoteObject.narrow() is required?
Very urgent
thanks in advance
 
Chris Mathews
Ranch Hand
Posts: 2712
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It is required for interoperability with RMI-IIOP. Every J2EE Application Server that implements EJB 2.0 is required to support RMI-IIOP.
If you are using an Application Server that supports a proprietary protocol (such as t3 for WebLogic) then using PortableRemoteObject.narrow() is not strictly necessary. However, for portability reasons it should still be used.
BTW, this only applies to Remote interfaces. Local interfaces do not need to use PortableRemoteObject.narrow().
 
william kane
Ranch Hand
Posts: 260
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Chris Mathews:
It is required for interoperability with RMI-IIOP. Every J2EE Application Server that implements EJB 2.0 is required to support RMI-IIOP.
If you are using an Application Server that supports a proprietary protocol (such as t3 for WebLogic) then using PortableRemoteObject.narrow() is not strictly necessary. However, for portability reasons it should still be used.

Thanks cris,
Am i right in concluding that portableremoteObject.narrow is mandatory if my appserver implements ONLY rmi-iiop.
I didnot get how t3 is used by weblogic.
william
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!