Hi Lawrence, Could you describe the scenario and the need for doing this, in detail? It would be great to understand and possibly re-use this strategy in future.
Cheers, Manav. At 04:56 PM 9/3/2002 +0200, Lawrence Marsh wrote: >Yes this is possible - we do this. > >Cheers > >Lawrence > >-----Original Message----- >From: Karr, David [mailto:[EMAIL PROTECTED]] >Sent: 03 September 2002 16:55 >To: [EMAIL PROTECTED] >Subject: Re: entity bean > > > > -----Original Message----- > > From: Manavendra Gupta [mailto:[EMAIL PROTECTED]] > > Sent: Monday, September 02, 2002 10:16 PM > > To: [EMAIL PROTECTED] > > Subject: Re: entity bean > > > > At 08:36 AM 9/2/2002 -0600, Mohammed Javid wrote: > > >Hi, > > > > > >please let me know on these > > > > > >1 Is this possible > > >To have different ejb names for the same ejb and refer each > > ejb name with > > >different jndi names and mention the parameters > > >like <finders-load-bean> and other attributes of each ejb > > seperately based > > >on different ejbname and jndi name > > >Or should we deploy the same ejb with different names and > > then only we can > > >specify different parameters to each ejb > > Why would you want to have multiple JNDI names for one bean? The very > > concept of JNDI relieves you from the hassles of having to > > locate and keep > > track of components (the COM equivalent of a GUID). > > Even if you strongly believe that you need to refer to the > > same bean with > > multiple JNDI names, there can only be a one-to-one > > association between the > > bean and the JNDI name - so, you would then need to deploy > > the bean with > > multiple times, though it still beats me if that would > > benefit you in any way. > >I don't know whether this is "useful", but it seems to me that it might be >possible to set up two different JNDI names which point to "beans" which >have the same home interface, same object interface (remote or local), but >different implementation classes, perhaps one a subclass of another, the >base class implementing CMP, and the subclass implementing BMP. This >pairing of base class and subclass is probably only practical in EJB 2.0. > >=========================================================================== >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". > > >Visit us at http://www.clearstream.com > >IMPORTANT MESSAGE > >Internet communications are not secure and therefore Clearstream >International does not accept legal responsibility for the contents of >this message. > >The information contained in this e-mail is confidential and may be >legally privileged. It is intended solely for the addressee. If you are >not the intended recipient, any disclosure, copying, distribution or any >action taken or omitted to be taken in reliance on it, is prohibited and >may be unlawful. Any views expressed in this e-mail are those of the >individual sender, except where the sender specifically states them to be >the views of Clearstream International or of any of its affiliates or >subsidiaries. > >END OF DISCLAIMER > >=========================================================================== >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".
