Carsten Ziegeler wrote: > Alec Bickerton wrote: >> Having spent most of today going through a mountain of .xsl, I have >> found the cause. It appears that if a transformation does this... >> >> <session:createcontext name="mysession"/> >> <session:setxml context="mysession" path="/sessionua"> >> .... >> </session:setxml> >> >> Then the session context hangs around and causes the Not serializable >> exception. >> >> Am I missing something? >> >> Does any mechanism exist to ensure this is removed at the end of the >> pipeline. >> > Ok, by this you create a *session* context, so the scope/lifetime of > this context is the session. Therefore it's not destroyed at the end of > the request.
Is it possible to create a context that explicitly has a scope of the request ? > Depending on your application and what you're doing there is the > temporary context (lifetime is a single request). So changing the first > line to > > <session:createcontext name="temporary"/> Thanks, that seems to have done the trick. Although I still need to do some more thorough testing, changing to use the temporary context, has made the NotSerializableException issue disappear. All the best, Alec --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
