>From: Rickard �berg <[EMAIL PROTECTED]>
>Reply-To: A mailing list for Enterprise JavaBeans development
><[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: ejb-link in deployment descriptor
>Date: Wed, 3 Jan 2001 14:21:07 +0100
>
>Hi!
>
>Heiko Gottschling wrote:
> > > Then, the Assembler takes a bunch of beans and package them into a
> > > logical application. Part of his work is to resolve ejb-ref's. This is
> > > done by looking at the <home> and <remote> tags and finding the
> > > appropriate beans to resolve them into. The Assembler hence adds the
> > > <ejb-link> element to the bean the ejb-ref should point to. When the
> > > Assembler is done there are no ejb-ref elements without a ejb-link
> > > child. So, now it is not optional although the DTD says it is. It is
> > > still syntactically optional, but semantically it is required after
>this
> > > step.
> >
> > I still don't quite get it. Two questions:
> >
> > 1) If the app assembler can find the appropriate beans by looking at the
> > <home> and <remote> tags, why can't the J2EE container itself do so
>(i.e.
> > find the referenced beans by their class names, rather than by
><ejb-link>)?
>
>There may be two or more beans with the same home/remote combo.
>
Hi Rickard!
Could you provide a scenario or two where deploying the same home/remote
combo multiple times is useful from an application architecture perspective?
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
===========================================================================
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".
