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 UnMarshal errors, not 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/Unmarshal-Error-CXF-2-1-6-vs-CXF-2-2-4-tp2799836p2799836.html Sent from the cxf-user mailing list archive at Nabble.com.
