You mean like a lookup method, ;-). Off the top of my head I would like to be able to define abstract methods in the component internals which would provide access to homes and get rid of the repetitive code such as new InitialContext(), ctx.lookuo(),etc......
Of course we would have to come up with a lovely method naming convention for locals and remote and multiple links to homes with different implementations but the same remote interface. This might also help the container align bean lookups in relation to its underlying load balancing mechanism (each major vendor does it differently). Another benefit is that its now in the interface and not something that can be mistakenly removed from the descriptor resulting in failure of the componet at runtime instead of deployment time. The current mechanism should still be supported to allow more dynamicism within the component. I have not given this much thought so feel free to bash me up. William -----Original Message----- From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]] On Behalf Of Vikram Naik Sent: 31 July 2002 10:04 To: [EMAIL PROTECTED] Subject: Reg Local Intreface in EJB 2.0 Hello All, In Ejb2.0 we have LocalHome and Local-Component Interfaces, which can reduce the unnecessary overhead of remote calls if the Ejbs are in same JVM. I was just pondering on one thought .... If the Ejb's are in same JVM then Why LookUP ???? ... can't there be some other mechanism to get the home object.... Thanks & Regards Vikram Naik 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".
