[jbossws-dev] Re: [Fwd: Re: Compatibility Between CP Releases]

[Thomas Diesler]

On Fri, 2007-11-23 at 15:55 +0200, Dimitris Andreadis wrote:
> The change in serialVersionUIDs is often unintentional and happens when no explicit 
> serialVersionUID is defined and a change is made in the class that recalculates a different 
> implicit Id. As Thomas pointed out, we fixed those ids in SP2.
> 
> We probably need to run probably something like JBoss-AS-4.2.x-CompatibilityMatrix for EAP.
> 
> Rajesh could help you setup it up.
> 
> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-4.2.x-CompatibilityMatrix/
> 
> At the same time the compatibility matrix testsuite doesn't include webservices tests, 
> AFAIK, so this is a possible TODO item.
> 
> Thomas, is there some kind of cross-version compatibility testing for WS happening already?

No, AFAIK there is not. We do however have public interop endpoints
setup.

http://jbws.dyndns.org/mediawiki/index.php?title=Interop_Endpoints

I also don't really understand the use case where a serialVersionUID
conflict would show up. The only use case I can think of is an appclient
deployment to jboss-4.x and a client vm doing a JNDI lookup of the
preconfigured stub using jboss-4.y libraries.

cheers
-thomas

> 
> Fernando Nasser wrote:
> > Dimitirs,
> > 
> > What was the idea behind the serialVersionUID change?
> > 
> > How do we handle applications using EAP 4.2 client taljing to EAP 4.3 
> > servers (as per compatibility rules)?
> > 
> > Any workarounds?
> > 
> > Cheers,
> > Fernando
> > 
> > Thomas Diesler wrote:
> >> This is possible. We changed the serialVersionUID as requested by
> >> Dimitris
> >>
> >> cheers
> >> -thomas
> >>
> >> [tdiesler at tddell jbossws-native-2.0.1.SP2]$ svn log -v -r4837
> >> ------------------------------------------------------------------------
> >> r4837 | thomas.diesler at jboss.com | 2007-10-21 08:40:22 +0200 (Sun, 21
> >> Oct 2007) | 1 line
> >> Changed paths:
> >>
> >> M 
> >> /stack/native/tags/jbossws-native-2.0.1.SP2/src/main/java/javax/xml/rpc/JAXRPCException.java 
> >>
> >>
> >> M 
> >> /stack/native/tags/jbossws-native-2.0.1.SP2/src/main/java/javax/xml/rpc/ServiceException.java 
> >>
> >>
> >> M 
> >> /stack/native/tags/jbossws-native-2.0.1.SP2/src/main/java/javax/xml/rpc/soap/SOAPFaultException.java 
> >>
> >>
> >> M 
> >> /stack/native/tags/jbossws-native-2.0.1.SP2/src/main/java/javax/xml/soap/SOAPException.java 
> >>
> >>
> >> Use serialVersionUID required by the tests
> >> ------------------------------------------------------------------------
> >>
> >>
> >> On Fri, 2007-11-23 at 11:57 +0100, Heiko Braun wrote:
> >>> something we may need to verify before the 2.0.2 release.
> >>> unfortunately i am stuck in meetings today and wasn't able to 
> >>> reproduce the problem yet.
> >>>
> >>> /heiko
> >>> email message attachment, "Forwarded message - Re: Compatibility
> >>> Between CP Releases"
> >>>> -------- Forwarded Message --------
> >>>> From: Fernando Nasser <fnasser at redhat.com>
> >>>> To: Heiko Braun <hbraun at redhat.com>
> >>>> Cc: Fernando Nasser <fnasser at redhat.com>, Deepak Bhole
> >>>> <dbhole at redhat.com>
> >>>> Subject: Re: Compatibility Between CP Releases
> >>>> Date: Thu, 22 Nov 2007 09:23:44 -0500
> >>>>
> >>>> Heiko Braun wrote:
> >>>>> so, no action item for me, right?
> >>>>>
> >>>> We need you to confirm or deny the following statement:
> >>>>
> >>>> "An application using the WS 1.2.1 client library cannot communicate 
> >>>> with a server using the new WS 2.0.1 due to serialVersionUID mismatch"
> >>>>
> >>>> And if you say yes, is there anything we can/should do to prevent that?
> >>>>
> >>>> Cheers,
> >>>> Fernando
> >>>>
> >>>>
> >>>>> On Thu, 2007-11-22 at 08:37 -0500, Fernando Nasser wrote:
> >>>>>> It seems to fall into this same class of problem.
> >>>>>>
> >>>>>>
> >>>>>> Carlo de Wolf wrote:
> >>>>>>> Fernando,
> >>>>>>>
> >>>>>>> On a related note: do you want this one in?
> >>>>>>> http://jira.jboss.com/jira/browse/EJBTHREE-1118
> >>>>>>>
> >>>>>>> Carlo
> >>>>>>>
> >>>>>>> On Wed, 2007-11-21 at 19:01 -0500, Fernando Nasser wrote:
> >>>>>>>> It seems that applications with older client libraries (like EAP 
> >>>>>>>> 4.2) using web services may have problems communicating with new 
> >>>>>>>> (EAP 4.3) servers because serialVersionUIDs changed between WS 
> >>>>>>>> 1.2.1 and WS 2.0.1.
> >>>>>>>>
> >>>>>>>> Heiko, can you confirm or deny that?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Ryan Campbell wrote:
> >>>>>>>>> Darran Lofthouse wrote:
> >>>>>>>>>> Do we have plans to actually perform the compatibility tests 
> >>>>>>>>>> between the
> >>>>>>>>>> different CP versions to ensure none of the changes will prevent
> >>>>>>>>>> different versions communicating with each other?
> >>>>>>>>>>   
> >>>>>>>>> What kinds of compatibility?
> >>>>>>>>>
> >>>>>>>>> What we have:
> >>>>>>>>> Serialization Static Analysis - Do the serialUID's match 
> >>>>>>>>> between versions?  All classes are checked.
> >>>>>>>>> Interop - do legacy client libraries work with the current 
> >>>>>>>>> server implementation?  Coverage here is across several 
> >>>>>>>>> services.  See 
> >>>>>>>>> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.2-compatibility-matrix 
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> What we don't have:
> >>>>>>>>> API compatibility - we don't currently have any tests for 
> >>>>>>>>> this.  There are reporting tools for comparing API's which we 
> >>>>>>>>> should consider for CP02, but we won't have time for CP01 since 
> >>>>>>>>> testing starts in about a week.
> >>>>>>>>>
> >>>>>>>>> Ryan
> >>>>>>>>>
> >>>>>>>>>
> >>>>>
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx