13.6.3 Container-Managed Transaction Demarcation for Message-Driven Beans
Only the NOT_SUPPORTED and REQUIRED transaction attributes may be used for message-driven bean message listener methods. The use of the other transaction attributes is not meaningful for message- driven bean message listener methods because there is no pre-existing client transaction context (REQUIRES_NEW, SUPPORTS) and no client to handle exceptions (MANDATORY, NEVER).
Joined: Sep 22, 2005
For an enterprise bean�s timeout callback method only the REQUIRES, REQUIRES_NEW and NOT_SUPPORTED transaction attributes may be used.
I think enterprise bean�s timeout callback method is also a business method. Therefore it can be call from client and can have REQUIRES_NEW attribute. The 2 other attributes I think explaining like MessageDrivenBean
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