One of the things mentioned in HFE is that MessageDrivenBeans should use only Required or NotSupported as Tx attributes.
But since the container calls the MDB's onMessage method, we can assume that the onMessage call is called without any tx context.
It will be like this when Required is used
onMessage (Tx A) Container ---> Container (no tx) (No tx)
Wont it be the same when when the RequiresNew is used too?
Also we assume that when the container calls NotSupports, it is calling without any tx context. If that is the case, why cant Supports be a valid attribute (because Supports and NotSupported will look the same)?
So why cant we use it them? [ November 21, 2004: Message edited by: Justin ]
Only the NotSupported and Required transaction attributes may be used for message-driven beans.
The use of the other transaction attributes is not meaningful for message-driven beans because there can be no pre-existing transaction context (RequiresNew, Supports) and no client to handle exceptions (Mandatory, Never).
Java Platform, Enterprise Edition 6 Web Services Developer Certified Expert Exam Study Guide and Quiz Exam 1Z0-810: Upgrade to Java SE 8 Programmer Study Guide and Quiz
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
subject: Why not use RequiresNew/Supports for MDB?