I believe that many, if not most, EJB client applications will use the current
thread to identify the context that is used for authentication. I am not sure
how you fix this without getting your InitialContext inside the thread that
is accessing the server. Personally, I really hate this aspect of Swing.
tim.
> We have built a J2EE application with a Swing GUI Rich Client (using the
> J2EE
> Reference Implementation application client container). When we added
> security
> to the EJBs, we found that if you call an EJB from a Swing event handler
> the
> security context is lost and the EJB container believes you to be guest.
> However, if you make the call from the main method, or a separate thread
> started from the main method, the security principal is propagated
> correctly.
>
> The output and code is included below. If anyone has seen anything like
> this
> before and knows why it may be happening, or better yet, what we can do
> to make
> it stop happening, your help would be greatly appreciated.
>
> Regards,
> Brett Beaumont
> Dale V. Georg
>
> ================================
> Dale V. Georg
> Technical Manager
> Indus Consultancy Services
> [EMAIL PROTECTED]
> (201) 261-3100 x229
> ================================
===========================================================================
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".
