Yes, Yes, maybe. I tried to keep the old config working, and there are some tests for it. In any case, the changover wouldn't be much XML editing.
On Mon, Jan 19, 2009 at 6:12 PM, relphie <[email protected]> wrote: > > > I would very much like to move to 2.1. However, I think the > incompatiblities between 2.0 and 2.1 make it almost impossible. I do have > a > few questions about migrating - > > Can a client generated with 2.0 connect to a service generated with 2.1? > Can a client generated with 2.1 connect to a service generated with 2.0? > Will the xml configuration for 2.0 work for 2.1? > > > Benson Margulies-4 wrote: > > > > This would require a complete re-debug of the original problem. 2.0.x has > > the more or less original XFire Aegis which got rewrote. Are you sure you > > can't move to 2.1. > > > > On Mon, Jan 19, 2009 at 5:49 PM, relphie <[email protected]> wrote: > > > >> > >> Hello, > >> > >> I was looking through the CXF code looking to backport the SortedSet fix > >> (https://issues.apache.org/jira/browse/CXF-1770) to cxf-2.0.9 by > >> re-registering an updated ComponentType. However, I cannot figure out > >> where > >> the original ComponentType gets added to the TypeMappingRegistry, so I > >> don't > >> know what to register my updated ComponentType as. Any help? > >> > >> Thanks, > >> > >> Brian > >> -- > >> View this message in context: > >> > http://www.nabble.com/CXF-SortedSet-type-mapping-tp21553393p21553393.html > >> Sent from the cxf-user mailing list archive at Nabble.com. > >> > >> > > > > > > -- > View this message in context: > http://www.nabble.com/CXF-SortedSet-type-mapping-tp21553393p21553756.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
