cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jbradfor <jbrad...@amfam.com>
Subject Unmarshalling error - CXF 2.2.4 vs CXF 2.1.6
Date Wed, 01 Sep 2010 17:53:53 GMT

We use CXF for Providers and Consumers here.

We added a single optional element to a complex type (2.2.4), regened and
deployed our Provider.

All Consumers who are running 2.1.6 continue on without errors or incidents.

All Consumers who are running 2.2.4 started blowing up with UnMarshall
errors, no recognizing the new Optional element.

Why is this and is there any workaround?

This puts a real big slow down in our development process, since we have to
create a new MAJOR version (essentially a whole new service), versus making
our contract backward compatible.
-- 
View this message in context: http://cxf.547215.n5.nabble.com/Unmarshalling-error-CXF-2-2-4-vs-CXF-2-1-6-tp2799670p2799670.html
Sent from the cxf-issues mailing list archive at Nabble.com.

Mime
View raw message