Ok.  I've done a bunch more reading and have a very rudimentary
understanding of J2EE, Connector, JMS, and EJB (2.0).

I really want an Entity Bean that can participate in a publish
subscribe model.  The idea put forth here was to wrap it in a
Message Driven Bean.  Yet Message Driven Beans are completely
anonymous.  So, that seems like it won't work directly.

Does this mean that I'd have to put data in my JMS message about
the entity bean I really want to deal with and then have the
anonymous message driven bean lookup that entity bean and basically
act as a proxy for it?

[Suppose I have a calcluate entity bean.  Different 'instances' of this
calculate bean calculate different functions.  I want to send a message
to one of them that some input data that they use changed so that it
can re-calculate.  Thus, these calculate beans are subscribed to topics
that correspond to the input data that they need - yet another matter, can
one dynamically create topics in JMS?]


That's all that comes to mind so far for using JMS in the EJB enviornment
for what I'd like.  I'd appreciate any other thoughts (or concurrence).

So much for obvious simplicity! <grin>

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

Reply via email to