This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
Created attachment 392 [details] explicit serialVersionUID patch