Author: buildbot Date: Wed Mar 21 21:48:03 2012 New Revision: 809488 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 Wed Mar 21 21:48:03 2012 @@ -127,14 +127,14 @@ Apache CXF -- 2.6 Migration Guide <h3><a shape="rect" name="2.6MigrationGuide-RemovedModules"></a>Removed Modules</h3> -<ul><li>cxf-common-utilites was merged into cxf-api</li></ul> +<ul><li>cxf-common-utilites was merged into cxf-api</li><li>cxf-rt-binding-http has been removed. It's been "deprecated" for a while and it's functionality has long been replaceable with the JAX-RS frontend.</li></ul> <h3><a shape="rect" name="2.6MigrationGuide-APIChanges"></a>API Changes</h3> <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></ul> + <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></ul>