Hi Dain,

Thanks for the info and the spec reference. It saved me the task of
going through the MDB part once again ;). Thanks again.

Regards
Manu


On 12/21/06, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
On Dec 20, 2006, at 3:31 AM, Manu George wrote:

> Hi David,
>        Yes pretty exciting ;). Will be looking forward to that in VM
> service being there. There is another thing that is missing in the
> code for MDB and that is Transaction Support.Should I open a JIRA for
> that? Actually most of the code is there but there are some gaps here
> and there which needs to be plugged. I am trying to add that after
> investigating how its done for Session beans. Now for an MDB with
> container managed transaction demarcation the only two supported
> Transaction policies are Required and NotSupported. What should be the
> behaviour if the user specifies any other Transaction policy in the
> deployment descriptor? Maybe I did not look hard enough, but I am
> unable to find the expected behaviour for this.
> Should it be defaulted to NotSupported or should there be an error
> thrown during the deployment process.

Ya, that is part of the EJB spec (3.0 section 5.4.12).  The only
allowed transaction types for a MDB is required, not supported and
bean managed.  For the timeout method, the spec additionally allows
the requires new transaction attribute.

-dain

Reply via email to