> The workaround is to restart JRun when
> you change a bean or a JSP that loads a
> bean (unless the bean hasn't been loaded
> yet), I think.
I think that the solution for this exception is to create a
serialVersionUID member in the Serializable bean or class that you
wish to store in a session. This is easily accomplished using the
serialver tool that comes with the JDK. You run this command with
the full name of the class that you wish to create a UID for. It
outputs the line of code that you should insert into the class file's
source. It is a classloader issue. When you make changes to a class
and recompile, any older versions of that class that are serialized
will not be able to be deserialized as the same class without having
the same serialVersionUID. Does this make sense? I am pretty sure
that this is what is necessary.
Larry
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
