Ok... does this imply that the receiving entity bean doesn't
need to be 'active' in some sense in order to receive the
message. That is, does the EJB environment (via JMS somehow)
activate the entity bean (wrapped in a MessageDriven bean).
I haven't read up yet on Message Driven beans so if this
is already all talked about please say so.
Joel
----- Original Message -----
From: "Ian McCallion" <[EMAIL PROTECTED]>
To: "Joel Riedesel" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, May 10, 2001 10:13 AM
Subject: Re: [EJB-INT] EJB Provider Design/Arch questions
> Joel Riedesel wrote:
> >
> > I've got a couple of what seem like architectural
> > questions regarding how to design a set of EJBs.
> >
> > In our current application we've got a concept of an
> > application and 'n' engines. Each engine handles a
> > particular kind of data processing.
> >
> > We use publish-subscribe quite heavily. An engine subscribes
> > to both other engines and the application on a fine-grained
> > level to be notified of changes that it can react to
> > and then do something about.
> >
>
> <snip>
>
> Joel,
>
> Why not use a pub/sub messaging system instead of building your own
pub/sub
> mechnism? You could still use Entity Beans for the data, but you'd need to
wrap
> them with MessageDriven Beans. It would make the whole thing much simpler.
>
> cheers... Ian
>
>
> ================================
> Ian McCallion
> Alexis Systems Limited
> Romsey, UK
> ================================
===========================================================================
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".
