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