If the observable (sender) has knowledge of who the
observers/listeners are, you can use the MessageDrivenBean as a
notification service. The observable delegates notification to the
MessageDrivenBean, and includes recipients as part of the message.
There will be just one instance of the
I've got a
message-driven bean listening to a topic. (Yes, I know, queues would be better,
but the queue/message driven mechanism has a problem, last I checked.) However,
every message causes a new instantiation of a message-driven bean... and since
it's a topic, it's feeding the message to
:12
PMTo: Orion-InterestSubject: message-driven beans from a
topic
I've got a
message-driven bean listening to a topic. (Yes, I know, queues would be
better, but the queue/message driven mechanism has a problem, last I checked.)
However, every message causes a new instantiation
What is the problem with message queues? I've used
them succesfully
--- [EMAIL PROTECTED] wrote:
I've got a message-driven bean listening to a topic.
(Yes, I know, queues
would be better, but the queue/message driven
mechanism has a problem, last
I checked.) However, every message
lto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, February 02, 2001 1:12 PM
To: Orion-Interest
Subject: message-driven beans from a topic
I've got a message-driven bean listening to a topic. (Yes, I know, queues
would be better, but the queue/message driven mec
