This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 2302 - explicit serialVersionUID
Summary: explicit serialVersionUID
Status: NEW
Alias: None
Product: DOM TS
Classification: Unclassified
Component: Java Binding (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Philippe Le Hegaret
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-25 23:51 UTC by Tom Tromey
Modified: 2007-03-29 18:50 UTC (History)
0 users

See Also:


Attachments
explicit serialVersionUID patch (777 bytes, patch)
2005-09-25 23:52 UTC, Tom Tromey
Details

Description Tom Tromey 2005-09-25 23:51:31 UTC
I'm working on GNU Classpath, which uses the w3c DOM java binding.
In our nightly API comparisons, we see a difference between the
DOM code we ship and the code in the JDK; see:

http://www.kaffe.org/~stuart/japi/htmlout/h-jdk14-classpath.html#err_minor_org_w3c_dom

The problem is that the serialVersionUID differs; presumably the reason
is that this depends on the compiler used to create the class file.  It is
most reliable to explicitly declare this field.  I'm attaching a patch to fix
this problem.

Having this patch in the upstream sources would help us get to 100% API
compatibility without requiring any local changes to code we don't maintain.
Comment 1 Tom Tromey 2005-09-25 23:52:13 UTC
Created attachment 392 [details]
explicit serialVersionUID patch