|Thread.currentThread().setContextClassLoader(container.getClassLoader()) or
|> something like that, before leaving the thread do the rest since the
|> ejbPassivate WILL work on the bean and need that visibility on
|its classes).
|
|This depends on if there is one passivation thread/bean or one p.
|thread/server. If one thread is used then this is needed, otherwise the
|CL should be inherited when the passivation startup code does new
|Thread(). Might be a good idea to add it in either case, just to be
|sure.
correct, I don't care if it is done at startup or each time, I would assume
he has a thread per container and then doing it at startup is enough.
marc
|
|/Rickard
|
|
|
|
|
|--
|--------------------------------------------------------------
|To subscribe: [EMAIL PROTECTED]
|To unsubscribe: [EMAIL PROTECTED]
|Problems?: [EMAIL PROTECTED]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
