Page 1 of 1

About Question enthuware.oce-ejbd.v6.2.469 :

Posted: Mon Apr 25, 2011 2:11 am
by ETS User
U are not saying this question is about a MDB in the description!!!


The onMessage method of a MDB can only have Required or NotSupported.



SOOO BUGGY UR TOOL

Re: About Question enthuware.oce-ejbd.v6.2.469 :

Posted: Mon Apr 25, 2011 6:16 am
by admin
The given answer is correct. As the explanation shows, you cannot use just about any transaction attribute value for any bean.

Re: About Question enthuware.oce-ejbd.v6.2.469 :

Posted: Mon Apr 25, 2011 2:12 pm
by Guest
yep, my fault, was too tired :P

Re: About Question enthuware.oce-ejbd.v6.2.469 :

Posted: Sat May 23, 2015 8:41 pm
by himaiMinh
Regarding to restriction on the transaction attribute,
the @PostConstruct and @PreDestroy methods run in unspecified transactional context for MDB, stateless and stateful bean.
So, even if the beans are CMT and the default attribute is REQUIRED, those lifecycle callback methods are still running in unspecified transactional context?

Re: About Question enthuware.oce-ejbd.v6.2.469 :

Posted: Mon May 25, 2015 1:54 am
by admin
Yes, life cycle callbacks are always in unspecified transaction context.