Its not always mandatory that EJBHomeObjects are just normal java objects, there might be corba compatible objects that have been exported for interoperability issues (RMI/IIOP comes into play then instead of RMI/*RMP) inwhich case the casting doesnt work and so a method call like PortableRemoteObject.narrow(home, home.class) would give us a proper reference to the Stub class to invoke Remote methods. If you are sure that the container has exported classes normally then casting is bound to work ! Hope this helps.
Regards, 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".
