svn commit: r874351 - in /websites/production/cxf/content: cache/docs.pageCache docs/30-migration-guide.html

[bu...@apache.org]

Author: buildbot
Date: Mon Aug 12 17:47:55 2013
New Revision: 874351

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/docs.pageCache
    websites/production/cxf/content/docs/30-migration-guide.html

Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/docs/30-migration-guide.html
==============================================================================
--- websites/production/cxf/content/docs/30-migration-guide.html (original)
+++ websites/production/cxf/content/docs/30-migration-guide.html Mon Aug 12 17:47:55 2013
@@ -121,9 +121,6 @@ Apache CXF -- 3.0 Migration Guide
 
 <p>Right now, 3.0 is in early planning stages.   This page is mostly collecting lists of things we are planning on changing.  It is by no means an exhaustive list and it may completely change depending on what gets done and such.</p>
 
-<ul><li>Combine api/core into just a cxf-kernel or similar, but pull out anything specific to the WSDL/SOAP based services into a rt/core-ws or similar to keep kernel lighter weight for pure REST apps.</li></ul>
-
-
 <ul><li>Combine the PhaseInterceptor and Interceptor interfaces and the PhaseInterceptorChain and InterceptorChain into a single set.   CXF only can really use the "Phase" versions and the others cause confusion and extra, unneeded interfaces.</li></ul>
 
 
@@ -145,6 +142,9 @@ Apache CXF -- 3.0 Migration Guide
 
 <h3><a shape="rect" name="3.0MigrationGuide-Workfinished"></a>Work finished</h3>
 
+<ul><li>Combined api/core into just a cxf-core.  All "wsdl" related stuff has been moved to a new cxf-wsdl bundle to remove the wsdl4j requirement for JAX-RS applications.</li></ul>
+
+
 <ul><li>CXFBusImpl has been removed.   The only subclass was the ExtensionMangerBus (SpringBus and Blueprint/osgi stuff subclassed that) so the functionality was pushed up into ExtensionMangerBus.  Some of the "common" methods were put directly on the Bus interface to make using the Bus cleaner (no casts to the impl).</li></ul>