I checked the jbossws sources (jboss-jaxrpc.jar, jbossws-core-src.zip) and there is no
SerialVersionUID defined for those classes.
I don't think those exceptions are serialized between WS peers, so normally there
shouldn't
be a problem. However, I remember we discussed this in the past and Ryan had some
objections, although I cannot find that post.
Scott had fixed that before, so there might be a reason for that:
http://jira.jboss.com/jira/browse/JBAS-2764?page=com.atlassian.jira.plugi...
So, it's either for Thomas to provide a jbossws 2.0.1.SP3 with a fix, or we change the
test
to ignore the mismatch, and re-tag AS 4.2.2.GA
Dimitris Andreadis wrote:
We had that issue in the past:
http://jira.jboss.com/jira/browse/JBAS-2764?page=comments
Those classes are now moved inside the WS project.
Rajesh Rajasekaran wrote:
> There is a mismatch on the SerialVersionUID's for the following three
> classes.
> javax.xml.rpc.JAXRPCException
> javax.xml.rpc.ServiceException
> javax.xml.soap.SOAPException
>
> in the jboss-4.2.2.GA release
>
> <testcase
> classname="org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase"
> name="test405Compatibility" time="67.739">
> <failure message="Failures on
> SerialVersionComparisson:javax.xml.rpc.JAXRPCException,
> javax.xml.rpc.ServiceException,
> javax.xml.soap.SOAPException"
>
type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError:
> Failures on SerialVersionComparisson:javax.xml.rpc.JAXRPCException,
> javax.xml.rpc.ServiceException,
> javax.xml.soap.SOAPException
> at
>
org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase.test405Compatibility(SerialVersionUIDUnitTestCase.java:122)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
> </failure>
> </testcase>
>
>
> The org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase has
> been silently failing on the continuous runs due to a classpath issue
> in the testsuite which i just fixed.
>
> Due to the JBossWS upgrade in 4.2.2.GA should we add these classes to
> the list of bad packages in the testsuite or is this something to
> worry about?
>
> THanks
> Rajesh
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development