Somehow we seem to have missed synching the javax.xml.bind.JAXBException
class serialVersionUID up with the j2ee1.4 value when we aligned these
in 4.0.2.
WARNING: No explicit serialVersionUID:
ClassVersionInfo{serialVersion=4092921986583236256,
hasExplicitSerialVersionUID=false, name=javax.xml.bind.JAXBException}
serialVersionUID error for javax.xml.bind.JAXBException, J2EE1.4
-1795805848732208234, current: 4092921986583236256
I rechecked the current j2ee1.4 ri value and it is consistent with the
testsuite serialVersionUID/j2ee141.ser value:
[EMAIL PROTECTED] lib]$ serialver -classpath jaxr-impl.jar
javax.xml.bind.JAXBException
javax.xml.bind.JAXBException: static final long serialVersionUID =
-1795805848732208234L;
We can use the org.jboss.j2ee.LegacySerialization system property to
correct this, but the check against the serialVersionUID/402.ser will
then fail and the JAXBException would have to be excluded from the
check, or the serialVersionUID/402.ser updated.
The big issue here is that I don't see how the
org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase passed
for the past releases. We can't have this test pass and latter have an
incompatibility like this show up. Either there is a flaw in the test or
what I'm seeing so I need to figure this out before 4.0.4RC1 goes out.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
