Thank you for the reply. Is that documented somewhere ? It means that putting
transaction attributes on methods that are called by the bean methods is not
correct and probably should n't be allowed.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172097#417209
zilbi is right. A plain Java call will not start a new transaction. You have to
invoke that method through the EJB object.
anonymous wrote :
| Also update(Record r) is marked as a private method and not defined in the
bean interface.
You will have to make it accessible through the interface.
So are the transaction related annotations on methods called from a bean method
not applied ?
Also update(Record r) is marked as a private method and not defined in the
bean interface.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170652#4170652
Reply t
not sure but i think what happens is the the call you make for update() are not
recognized by the container as ejb calls and that's why a new transaction is
not opend.
think you need to get a ref to this ejb using the session context and invoke
update using it. should look something like thatYo
