Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <41F02EBD.5000203@dslextreme.com>
Date: Thu, 20 Jan 2005 14:20:45 -0800
From: Ralph Goers <Ralph.Goers@dslextreme.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: Session serialization
References: <41EFD443.8020908@zorel.org>
In-Reply-To: <41EFD443.8020908@zorel.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Aur�lien DEHAY wrote:

> 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.
>
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.

Ralph

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org