Hey
marc fleury wrote:
> btw I think more about this and we really have 4 points of entry with
> threads...
>
> 1- normal invocation (enters through container invoker)
> 2- commit through Synchronization (session and entity)
> 3- passivation (independant thread)
> 4- time outs
>
> on ALL these 4 entries the context class loader must be set, the error we
> are seeing is in 2 but all the others must be done (well 1 is done at
> least).
>
> Simone can you look into 3 (do
> 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.
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
