> -----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".
