Lewis,
Maybe you are still living into the ejb1.0 spec. The logic has changed. With
ejb1.0
you got the possibility to change the identity of the calling thread using
setRunAsIdentity(), so you could face the problem you outlines below. With
ejb1.1,
the getCallerPrincipal() will always returns the identity of the user that
originate the
thread (the first caller). The caller's identity is no longer associated with a
particullar
caller in the chain.
The better solution is: move to ejb1.1
Regards.
Francis.
"Lewis, Brent" wrote:
> All,
>
> Is there a way to retrieve calling chain information from the lowest
> level of a bean call? For instance, consider an EJB "system" which begins
> with a call to a session bean A, which in turn makes a call to another
> session bean B. B then makes a call to an entity bean C. Is there a way for
> C to get A's identity information? I know that C could use its EntityContext
> and use the getCallerIdentity() method to retrieve information about B, but
> then is there a way to get A's information? This example is very elementary
> to the problem that one could face...what if there were 10 calls in the
> calling chain? Any information would be appreciated.
--
Francis Pouatcha
MATHEMA Software GmbH
http://www.mathema.de
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
