Chip, Rickard,
Absolutely, it should be possible to implement the same set of interfaces
in multiple ways. This is one of the basic principals of object-oriented
programming: polymorphism.
That being said, I know there are products on the market that allow only
a single implementation of a given set of EJB interfaces. I am amazed that
users don't find this to be a completely unacceptable limitation.
-jkw
Rickard �berg wrote:
>
> Chip Wilson wrote:
> > > > 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?
>
> I could try 8-)
>
> The bean FormProcessingBean processes forms and on completion can
> optionally send a notification to interested parties. The notification
> is done by calling another bean that uses the Notification and
> NotificationHome interfaces. There are two implementations of these
> interfaces: EmailNotificationBean and LogNotificationBean. The ENB sends
> an email to a configured address, whereas LNB adds a log entry to a log.
>
> Two ENB and LNB beans are deployed with the same interfaces, and
> ejb-ref's to them are added to the FormProcessingBean. After completion
> of a form processing the FPB notifies both the ENB and LNB beans which
> perform their respective notification procedure.
>
> Sounds reasonable?
>
> /Rickard
===========================================================================
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".
