tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Cheshire <>
Subject Re: serializable class not persisting (long email)
Date Mon, 05 May 2003 18:55:00 GMT
Hi Yoav,

Shapira, Yoav wrote:

>It doesn't seem like the problem is in the actual
>serializing/de-serializing of the class.  You don't get a
>readObject/writeObject exception nor a SerializationException.
>It seems like the class is not found during session archive
>de-serialization.  Try putting the jar with the class in it in
>common/lib instead of WEB-INF/lib and see if that makes a difference.
I tried moving the class into the jar used for all my other serializable 
objects (shared between multiple apps), and it didn't find them.
&*%^^% I moved the jar into common/lib like you suggested and it worked, 
but nothing else did. Why? My other serializable classes are in the 
WEB-INF/lib and they work fine. Putting them into the common/lib 
directory is not a feasible solution as the filesystem permissions do 
not allow it (tomcat is owned by root).

I am completely confused. Tomcat finds the class when compiling and 
accessing the JSPs and servlets, just not while persisting. Is there 
something wrong with the class name that it is causing a clash somewhere?

>Also, the [Lextras.SearchResult indicates an attempt to de-serialize an
>array of SearchResult items, not just one SearchResult instance.  This
>is fine, just wanted to make sure you were aware of it.
Yes it is an array. I was curious at that notation. I tried reloading 
the context when an array of different objects was in the session and 
they persisted and reloaded just fine.

What can I do to fix this?



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message