This should help u... J2EE applications are required to use the RMI-IIOP APIs (specifically the narrow method of javax.rmi.PortableRemoteObject) when accessing Enterprise JavaBeans components, as described in the EJB specification. This allows enterprise beans to be protocol independent. In addition, J2EE products must be capable of exporting enterprise beans using the IIOP protocol, and accessing enterprise beans using the IIOP protocol, as specified in the EJB 2.0 specification. The ability to use the IIOP protocol is required to enable interoperability between J2EE products.
vikram > -----Original Message----- > From: A mailing list for Enterprise JavaBeans development > [mailto:[EMAIL PROTECTED] Behalf Of Manoj Kumar > Sent: Tuesday, March 18, 2003 10:30 AM > To: [EMAIL PROTECTED] > Subject: PortableRemoteObject.narrow > > > Hi, > I have a doubt regarding the usage of the > PortableRemoteObject.narrow(...) method in the clint code to lookup the > EJB Home Object. Actually, my doubt is that even a simple casting can > also > work very well then why do we need to use the > PortableRemoteObject.narrow(...) method. Is it safe enough to with just > the simple Casting??? In what scnerios one should use the > PortableRemoteObject.narrow(...) . Any pointer to a good documentation > will be of great help. > > Thanks & Regards, > Manoj Kumar. > > ================================================================== > ========= > 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".
