Lou Bona wrote:
>
> I think you misunderstood, or maybe I did, but I thought the question became:
> can a client calling an EJB
> be running in a thread?
>
> I can't see any reason the server would even be aware that the calling process
> is running in a thread
> separate from the main thread of a client application (in a different VM). Or
> that the multiple clients
> hitting it are all spawned from the same process. However, my experience is
> limited to weblogic and
> I don't have the spec handy.
Yes, the *client* of an EJB may be running in its own thread; the
appserver is responsible for serializing access to the bean. What
*cannot* occur is for that bean to then start its *own* thread, or to
call something else that might possibly result in the creation of
another thread.
IMHO the latter restriction, though perhaps hard to solve, needs to be
addressed, because this now means that I have to take great care not to
call my vast array of third party software from an EJB because one of
those third party software components *might* create a thread, and the
only way to know for sure is to call their tech. support department.
Isn't this what OO programming is supposed to avoid?
Cheers,
Laird
===========================================================================
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".
