• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Stateful Session AfterCompletion( )....

 
Harvey Chan
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Why accessing Resource Manager and EJB is not allowed here?
Any reason behind?
I think the client secruity context still here because
it allowed us to use isCallerinRole() method..
Thanks for helping me always......
Yours,
harvey
 
Philippe Maquet
Bartender
Posts: 1872
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Harvey,
I think that - by definition - you're in afterCompletion() *out of* a meaningful transaction context.
Best,
Phil.
 
Harvey Chan
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yup, I agreed that the transaction should not be there anymore.
However, in the definition, the rule for accessing resource manager
and EJB is releated to EITHER transaction context OR client security
context.
So, if the client security context still there ( as proved by isCallerInRole() ), then why we can't access the recource manager ( because the rule said
OR not AND)
I started to think the specification is really confusing....
Harvey
 
Jacky Chow
Ranch Hand
Posts: 63
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi Harvey,
I think the restriction is just a contract provided by the spec, without this contract, that is, the developers can access resource managers and EJBs, then the developers must handle complex issues of failure recovery.
Since the spec provides such contract, the developers gain the benefits of transaction handling provided by the Container!
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic