Rickard �berg wrote:
> Joel Crisp wrote:
> > It applies to the thread used by the EJB container. So any classes methods
> > called by that thread will be restricted. You need to pass an asyncronous
> > request to a thread outside the EJB container to access this
functionality.
>
> This is not correct. It is related to ClassLoaders as outlined in my
> previous posts. If it was related to the thread then..
I think I'm losing something in the context of this discussion.
Are you saying that none of the restrictions (threads, I/O, etc.)
have anything to do with the thread originating from the client's
invocation of the bean method? I find this hard to understand,
since the security and transactional context is dynamically set
based on the particular client access that's occurring. Please
explain.
I'm not having much success locating messages where you describe
how class loading relates to the restrictions. Would it be
possible for you to post a brief summary, or to point me to some
particular messages, or date ranges, or something?
Thanks,
Paul
===========================================================================
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".
