Server implementation objects may either inherit from javax.rmi.PortableRemoteObject or they may implement a remote interface and then use the exportObject method to register themselves as a server object. If its the first way that a container implements RemoteObjects for EJBHome then one has to use PortableRemoteObject.narrow which works fine for both ways of server implementation(other way is using exportObject after implementing a Remote interface as said above). To make the EJB code more portable (prior to J2EE1.3) it was recommended to use PortableRemoteObject.narrow but in J2EE1.3 its been made mandatory ! Hope this helps !!
Cheers, Kris -----Original Message----- From: Ashwani Kalra [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 09, 2002 4:03 PM To: [EMAIL PROTECTED] Subject: PortableRemoteObject.narrow Hi, Why its asked to use PortableRemoteObject.narrow(home, home.class) instead of just downcasting. The specs mention it is due to rmi-iiop compatibility. Can any body explain in more details about it. TIA Ashwani Kalra =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help". =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
