Aurélien DEHAY wrote:
Cocoon is not a distributable application, as defined by the Servlet spec. You will find that quite a few non-Serializable objects are stored in the session. CocoonComponentManager is pretty much what it sounds like. It keeps track of all the components that have been configured and are available for use. As you can imagine, Serializing this would make very little sense. I have no idea why it is being stored in the session though.Hello.
I'm trying to serialize my sessions with the persistance manager of tomcat to not loose them between during a restart.
I use session-context to store XML in my session and use a flowscript to handle my login logic (maybe it's not the sexyier way, but that's the way I do it).
When I shutdown my tomcat (tested with tomcat 5.0.28, 5.0.30 and 5.5.4), I've got the following error:
java.io.NotSerializableException: org.apache.cocoon.components.CocoonComponentManager.
What is this object? I've tryied to invalidate my continuations objects in the flowscript without any success. Is anyone knows a solution?
Regards.
Not directly but the Flowscript scope has access to e.g. the Cocoon service manager and the serialization process serializes the complete object graph.
A few weeks ago I had some discussions with Torsten, Chris Oliver, Sylvain and Vadim I think the problem should be solvable.
I'm going to keep the list updated about my experiences and I opened an issue at bugzilla (http://issues.apache.org/bugzilla/show_bug.cgi?id=33324)
-- Reinhard
