At pag 80 of EJB 2.0 spec the table specifies that for ejbCreate is
possible to make an access to a Resource manager but ejbCreate is
associated with a unspecified transaction context and this seems in
contrast with the affermation that accessing resorce managers and
enterprise beans is disallowed in the session bean methods for wich the
Container dos not have a meaningful tx context like declared in the specs.
Thanks in advance !
posted 12 years ago
It struck me too in the beginning and i reasoned as below. If someone knows better, then pls let us know
For BMT, the bean can use UserTransaction to start a transaction. So, it can call on resource manager's methods and other enterprise beans.
For CMT, probably the bean can call other enterprise beans which (probably) do not need a transaction and can manage their own transaction. I am not sure what the bean can do with Resource Managers.
Same for a Stateless session bean, it can call getUserTransaction in it's ejbCreate but cannot use any of its methods. So, it can just hold on to it. Its something like "being allowed a cake but it's just too soon to eat it".
SCJP, SCWCD, SCBCD
What are you doing? You are supposed to be reading this tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads