Couldn't they DELEGATE? That is, create an EJB of their own that leverages yours? It's possible that they couldn't, but, just curious.
Juan Pablo Lorandi Chief Software Architect Code Foundry Ltd. [EMAIL PROTECTED] Barberstown, Straffan, Co. Kildare, Ireland. Tel: +353-1-6012050 Fax: +353-1-6012051 Mobile: +353-86-2157900 www.codefoundry.com > -----Original Message----- > From: A mailing list for Enterprise JavaBeans development > [mailto:[EMAIL PROTECTED]] On Behalf Of Downey, Tim > Sent: Thursday, April 18, 2002 7:28 PM > To: [EMAIL PROTECTED] > Subject: Re: Best practices question for re-use of 3rd party EJB jar > > > Chris, > > Thanks for you suggestion. > > Our entities are EJB 2.0 and I'm planning on suggesting that > our customers use ejb-ql for the finders, but that still > doesn't solve the problem that they would need to "extend" or > replace the home interface that I distribute. > > It seems like the assembler/deployer role falls a bit short here... > > -tim > > -----Original Message----- > From: Thompson, Chris [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 18, 2002 1:35 PM > To: [EMAIL PROTECTED] > Subject: Re: Best practices question for re-use of 3rd party EJB jar > > > Tim, > > For your question it seems more like a situation where you > could use EJB 2.0 in which one could specify new finder > methods in the home interface and their implementation > declaratively in the deployment descriptor via ejb-ql, > assuming you are providing CMP entity beans. Just a suggestion. > > Chris Thompson > Bean-test Developer > http://www.empirix.com > > -----Original Message----- > From: Downey, Tim [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, April 17, 2002 10:26 AM > Subject: Best practices question for re-use of 3rd party EJB jar > > > Hi, > > We're developing an EJB application and will be distributing > several EJB jars. We intend for our customers to write code > to use our beans and then package their custom code plus our > EJB jars into an EAR file for deployment. > > We anticipate that our customer will be able to modify the > deployment descriptor or jndi-definitions file in order to > configure data sources, queue sources, etc, but I'm trying to > develop a solution for a problem that can't be addressed in this way. > > There are entity beans in the EJB jar that I am distributing. > I expect that our customers will want to utilize these > entity beans, but will probably have the need to add finders > to them. Is there any way for the assembler/deployer to > modify or add finders to an existing EJB jar? > > This really seems like a situation where I need EJB > inheritance. Does anyone have any suggestions that may help > with this? > > Regards, > -tim > > ============================================================== > ============= > 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". > =========================================================================== 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".
