Hi all !
Ok, we know that beans do not support threading. Now here is the thing :
We have a bean which uses a set of classes (package "business"). These
classes are used to access the data we need. Part of our data is accessible
from a server (our FXServer). So the business class access the FX Server by
declaring an FXServerConnection (from package fx). This worked perfectly.
Now we wish to have the FXServerConnection threaded. Of course, it does not
work, since the FXConnectionHandler (used by the FXConnection) extends
Threads. But I was wondering : if the FX package is in the lib directory of
my ejb container,. would it be possible to access it via JNDI, so the
FXServerConnection would not actually be in the same context as my EJB and
this way I would evade the restriction ?
The thing is that the FXServerConnection does not try to access the
business classes from within the thread, the bean calls invoke() on the
connection, that connection init the thread and wait for the response and
simply returns...
Is this possible ?
===========================================================================
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".
