Author: buildbot
Date: Tue Mar 27 19:48:04 2012
New Revision: 810275
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/26-migration-guide.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/docs/26-migration-guide.html
==============================================================================
--- websites/production/cxf/content/docs/26-migration-guide.html (original)
+++ websites/production/cxf/content/docs/26-migration-guide.html Tue Mar 27
19:48:04 2012
@@ -135,7 +135,7 @@ Apache CXF -- 2.6 Migration Guide
<ul><li>All API's that take or return "generic" classes have been update to
properly define the generic part. For example, methods like:<br clear="none">
"Class getServiceClass()" have been updated to be "Class<?>
getServiceClass()"</li><li>To resolve some of the "split-package" issues
between jars, SOME (very few) classes did have their packages changed.
<ul><li>org.apache.cxf.jaxb.JAXBUtils ->
org.apache.cxf.common.jaxb.JAXBUtils (and a couple other classes in that jaxb
package)</li><li>Many of the internal "Impl" classes and "Managers" (like
BindingFactoryManagerImpl, CXFBusLifeCycleManager, etc...) have moved into
org.apache.cxf.bus.managers. Users should always rely on the interfaces they
implement anyway.</li></ul>
- </li><li>The selectedConduit field of AbstractConduitSelector has been
removed as a ConduitSelector may be used to select multiple conduits depending
on scenarios and the selectedConduit field may not accurately reflect the
conduit that had been selected depending on the state of the threads, clients,
etc...</li></ul>
+ </li><li>The selectedConduit field of AbstractConduitSelector has been
removed as a ConduitSelector may be used to select multiple conduits depending
on scenarios and the selectedConduit field may not accurately reflect the
conduit that had been selected depending on the state of the threads, clients,
etc...</li><li>org.apache.cxf.tools.common.DataTypeAdapter has been deprecated
and moved to org.apache.cxf.xjc.runtime.DataTypeAdapter in a new runtime jar
that is part of the cxf-xjc package. This allows using the runtime without
bringing in all the CXF tooling dependencies. The DataTypeAdapter doesn't have
any other CXF dependencies and thus is usable outside of CXF as well.</li></ul>
