[jdom-interest] serialVersionUID for JDOM classes

[Michael Salmon]

I've had the same exceptions but I attributed them to the fact I was using
java 1.1 and ported jdom to use the collections classes. I did add
the serialVersionUID but that didnt help. Now I assume it's a larger problem
but I don't see what it could be. I've ended up (for now) just packaging 
the parser with jdom to create the document object on the fly from xml.
I should try an older jdom.
Are you using the same jvm to deserialize that you serialized with?

ms-

On Fri, May 24, 2002 at 05:32:36PM -0400, Andres March wrote:
> I am not having fun anymore.  I am going to have to roll back to using b6 unless I figure this out by the end of the day.
> 
> In order to eliminate compiler differences, I decided to use the binary of jdom.jar instead of compiling the classes into my own jars.  No luck.  The below error occurs.  I have seen many posts regarding this problem from last year.  I don't know why it only started affecting me when I upgraded to b8.  Oh well.
> 
> If anyone is interested:
> 
<snip> 
> 
> -----Original Message-----
> From: Michael Salmon [mailto:ms at speakeasy.net]
> Sent: Friday, May 24, 2002 2:07 PM
> To: Andres March
> Cc: JDOM list (E-mail)
> Subject: Re: [jdom-interest] serialVersionUID for JDOM classes
> 
> 
> Even adding them by hand didnt save me from getting ClassCastEXceptions
> when deserializing Documents in an applet. So I'm not sure it really would
> help across the board. Especially that its not even a release yet. It's
> definitly not a standard thing projects do either.
> 
> ms-
> 
> On Fri, May 24, 2002 at 04:53:56PM -0400, Andres March wrote:
> > Is there a reason serialVersionUIDs are not implemented in JDOMs source
> > files?
> > 
> > -Andres
> > _______________________________________________
> > To control your jdom-interest membership:
> > http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhost.com