If you do ever want mulitple onMessage listeners on a single consumer, it is
simple enough to define a ChainedMessageListener/MultiplexMessageListener
utility class that farms out the message events to many interested parties
in whatever way you like.
On 2/3/07, Robert Godfrey <[EMAIL PROTECTED]> wrote:
Hmmm... I think it *should* throw an Exception :-)
The JMS Spec is exceedingly woolly in places, and there are often seeming
contradictions between the speicification document and the JavaDoc of the
API.
From the spec (which is where my brain is at at the moment):
"It is important to note that clients rely on the fact that no
messages
are
delivered by a connection until it has been started. JMS providers
must
insure
that this is the case."
Which I take to mean that calling receive() should not receive a
message...
however the JavaDoc makes no mention of what it should do if called when
the
connection is stopped.
Of course, in .NET you're not implementing JMS so you are free to do as
you
like :-)
-- Rob
