I read in HFE p.460 as well as in spec 15.4.8 p.317 that if the message driven bean uses container managed transaction demarcation, message acknowledgment is handled automatically as a part of the transaction commit. (that is, if I unserstand well, if transaction commits, the receipt will is acknowledged by the container and if the transaction fails, no receipt and the JMS provider will resend the message).
But, as far as I know, it's allowed to specify two attributes for a transaction in CMT: Required and NotSupported. For Required, what the spec explains is OK, because there's a valid transaction context. But if NotSupported is specified, there's no valid transaction context present and I don't understand how in this case, acknowledgment should be tied to the transaction. In this case, should'nt we use the tag <acknowledge-mode> too, as we do for BMT?
Thanks for youe responses, Regards, Cyril. [ November 15, 2004: Message edited by: cyril vidal ]
I think there is nothing in EJB 2.0 related to NotSupported and auto-aknowldege But we know the NotSupported is unspacifed transaction context and for this type of Trancsation context the EJB 2.0 does not have proper specification how container should implement this unspacified context see 17.4.1 of ejb specs and 352 page for this.
So when we chose the MDB with the Unspacifed tracsaction context we are not going for the assured message processing after delivery in onMessage() so here the Transaction acknowlege-mode dose not play part in case of CMT.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com