• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

StatefulSessionBean - regarding

 
Sub swamy
Ranch Hand
Posts: 121
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
According to spec. Page 80, from with setSessionContext() method of a stateful session bean, we cannot call getCallerPrincipal() method.

For a stateful session EJB, when the setSessionContext method is run , there must have been a user who had called create which starts off the instantiation process � new instance, setSessionContext, ejbCreate. At this time why isn�t the sessionContext able to call getCallerPrincipal, isCallerInRole() methods?

Also, what happens between setSessionContext and ejbCreate methods such that in the latter we are able to call getCallerPrincipal() method?(spec. Page 80)
 
Roger Chung-Wee
Ranch Hand
Posts: 1683
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The purpose of setSessionContext is just to enable the storage of the reference to the SessionContext in an instance variable.

It is in ejbCreate where you can really start doing things as the object has been changed to an EJB. This is why client security information becomes available for the first time.
 
Mike Pandey
Ranch Hand
Posts: 62
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
But Roger, In setSessionContext(), we have the context instance available which is the lifeline to the container....so i don't quite understand why the client security info shudn't be avaliable out in the setSessionContext()methd.
pls advice.

thanks
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic