Yogaraj, Both EJBObject and EJBHome extends from java.rmi.Remote interface. Therefore, it should be at least, theoretically possible to export and bind any such objects (e.g. EJB objects), Which implement these interfaces into RMI Registry and do a subsequent lookup. EJBs are built around RMI-IIOP. However, there could be some problems in using RMI instead of JNDI as... 1) Calls through JDK's default RMI Registry are unsecured, you might have to right your own Custom socket factory for secured implementation or look for some alternative RMI Registry providers. 2)Almost all J2EE app servers are designed and geared to use JNDI infrastructure, as such, you might need to carefully investigate further about efficiency of EJBs in appserver runtime w.r.t factory for EJBs, instance pooling and instance swapping..., if you have RMI registry instead of JNDI. 3)If need be, pls. also check how would you involve JTA through pure RMI lookups... 4)Extending Rajesh's point, you can have a RMI wrapper over EJB layer, but then it introduces extra layer, more complexity, more proxy objects, more remote calls...which may not do any good...
Is there any special reqmt. for your client preferring RMI over JNDI? Ideas welcome. Regds, BJ -----Original Message----- From: Jayaprakasam, Yogaraj (Cognizant) [mailto:[EMAIL PROTECTED] Sent: Friday, March 28, 2003 11:53 AM To: [EMAIL PROTECTED] Subject: Re: EJB through RMI! Hello Rajesh, Thank you very much for your reply. Actually I never worked much on RMI before. Since my client is so keen on using RMI look am just wondering would extra benefit would he get by using RMI look up. I understand the simplicity and the advantages of using JNDI lookup. But I am just wondering, is there any advantage using RMI look up over JNDI. And also If the client is so keen on RMI look up. Is there a way to do it? Thank you for your time. Regards Yogaraj -----Original Message----- From: Rajesh S R [mailto:[EMAIL PROTECTED] Sent: Friday, March 28, 2003 11:30 AM To: Jayaprakasam, Yogaraj (Cognizant) Subject: RE: EJB through RMI! Hello Yograj, U can access the EJB home only thru JNDI lookup. I couldnt get why u r not directly looking up the EJB's thru JNDI from the client. If the problem is of exposing ur architecture use FrontControllers. The method u've told have some drawbacks. 1) It's addition of one unwanted layering. U access the EJB thru JNDI lookup from RMI Server. U cannot get rid of the JNDI access. U can have the handle only after having the home reference. The handles r essentially used to have the reference to the home over a period of time. 2) The usage of Handles have some problems. Handles can do nothing as its own. If the business methods have to be executed, home reference has to be reconstructed before trying it. Both these will affect the performance. For ur case, i cannot see the need of RMI lookup from the reqmnts. u'v given. JNDI - always preferred for its simplicity. The underlying impl is provided by the appln. server provider. JNDI to lookup a vast array of services using a simple API. RMI lookup - only for lookup of RMI services. Refer the specs or online tutorials for more details. Hope its clear. Best regards, Rajesh -----Original Message----- From: Jayaprakasam, Yogaraj (Cognizant) [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2003 9:47 PM To: [EMAIL PROTECTED] Subject: EJB through RMI! Dear Friends, i have a java thick client (Swing client) to call an ejb sessionbean but lookup should not be through JNDI it had to be acomplished thru rmi, We would like to have rmi on the server and have the stub of the rmi on = the client side which will get the ejbhome handle to the client. Is it possible? How can I achieve this?=20 And also, i would like to know the pros & cons of JNDI and RMI lookup. = Because our client demand is to lookup through RMI, it would be nice if = I can get the pros & Cons, to enable me to discuss with the client. I = believe that the bunch of experts here can surely help me in this. Thanks in Advance Regards Yogaraj DISCLAIMER: Information contained and transmitted by this E-MAIL is proprietary to Mascot Systems Limited and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If this is a forwarded message, the content of this E-MAIL may not have been sent with the authority of the Company. If you are not the intended recipient, an agent of the intended recipient or a person responsible for delivering the information to the named recipient, you are notified that any use, distribution, transmission, printing, copying or dissemination of this information in any way or in any manner is strictly prohibited. If you have received this communication in error, please delete this mail & notify us immediately at [EMAIL PROTECTED] Before opening attachments, please scan for viruses. ==========================================================================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".
