dan benanav wrote:
>
> > The specification is written in such a way as to allow server/container
> > vendors to attach arbitrary container-stuff as thread-local data in
> > container-managed threads. Any attempt to use the server's EJB infrastructure
> > from within a user-managed thread may result in the server attempting to locate
> > the container-stuff for the invoking thread, even if that thread is acting only
> > as a client to other beans. User-managed threads don't have any container-stuff,
> > thereby it might not work.
>
> So suppose from the main thread I create a new thread and do the above. (Get the
> InitialContext, etc.). Such a thread doesn't have any container-stuff either. So
>how does that
> work?
Which "main thread" are you referring to?
Anyway, assuming you meant the "main thread" in your client which is my best
guess at your intended meaning, the container-stuff I refer to is not
necessarily required for client threads. It all depends on the vendor
implementation. With Sybase EAServer, there is container-stuff that is only
required on the server side, and we now provide a thread management API for
use by components that require it.
________________________________________________________________________________
Evan Ireland Sybase EA Server Engineering [EMAIL PROTECTED]
Wellington - New Zealand +64 4 934-5856
===========================================================================
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".
