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. 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"/> might solve your problem. HTH Carsten -- Carsten Ziegeler [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
