> >> Hiram is the one who did the transaction parts of the MDB, but I would
> >> geuss this is what is going on: An MDB is ALWAYS transacted (the receipt
> >> that is), the flags only determins under what TX context the bean is
> >> invoked. This mean there will allways be a transaction going on under
> >> the hood.
> >
> > Is that by design... that NotSupported still runs with a TX?
>
> Yes, but remember. The receipt is under a transaction, but not the bean.
Ah, so it waits for onMessage() to complete.
Is the TX only for removing from the queue/topic? Will this same TX be used
by component invocations done by the MDB in NotSupported? Sorry, I am still
getting the hang of how EJB & JMS transactions really work.
Perhaps in this situation the receipt tx should be committed just prior to
calling onMessage()?
What are your thoughts about adding support for the MDB system to use an
optional dynamic policy to indicate if it should accept messages? you know
instead of simply blindly taking messages from the queue/topic. Perhaps
the dead letter support can be augmented to take a policy interceptor chain?
I would like to use MDB simplicity to process messages, but also make use of
JMS as a load balancer. Right now I could simply have onMessage() throw
exceptions to indicate non-interest, but that is just plain crazy.
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
