-
15. Re: Transaction Demarcation
Oh, it's not re-entrant, its sLsb called by sFsb. Anyway, enable logging (no, I don't search the Wiki for you) and don't guess.
-
16. Re: Transaction Demarcation
Hi Christian,
thanks for you help. That seems to be the reason.
I introduced another session bean and now its working! -
17. Re: Transaction Demarcation
Well my last post actually refers not to your last post, but the one before.
What you assume in your last post I thought before and made all the session beans stateful - but that did not help either.
It's seems to be that on reentrant calls the annotations are ignored. By introducing another SFSB I made the call non reentrant and now it works!
Thanks again! -
18. Re: Transaction Demarcation
Toni,
I am trying to do exactly what you describe but am having no luck. Could you possibly give a small example of how you achieved the transactions?
many thanks,
Dustin -
19. Re: Transaction Demarcation
When you call a method from within a session bean on the same bean, you have to call it using the interface (if you want transaction attributes to work, and any other interceptors).
You are probably calling on 'this' at the moment, which means the container doesn't get a chance to do its magic.
You can use the SessionContext (ejb api) to get the interface, and make the call on that.
The sessioncontext can be injected (if i recall correctly, put @Resource at the field).
Then, getBusinessObject should do the trick.