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

[bu...@apache.org]

Author: buildbot
Date: Thu Apr 11 15:48:01 2013
New Revision: 858129

Log:
Production update by buildbot for cxf

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

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

Modified: websites/production/cxf/content/cache/main.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 Thu Apr 11 15:48:01 2013
@@ -123,12 +123,12 @@ Apache CXF -- 3.0 Migration Guide
            <div class="wiki-content">
 <div id="ConfluenceContent"><h2><a shape="rect" name="3.0MigrationGuide-3.0MigrationGuide"></a>3.0 Migration Guide</h2>
 
-<p>Right now, 3.0 is in VERY 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>
+<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 common-utilities/api/core into just a cxf-kernel or similar.</li><li>Pull the "wsdl" specific stuff from kernel into a webservices base package that the webservices related things can pull and jaxrs doesn't have to.</li></ul>
+<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>Resolve all the split package things that prevent the OSGi bundling from working well.</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>
 
 
 <ul><li>Likely move some of the other Abstract classes and such from kernel.   For example, we now have a transports-common module.   Move the AbstractDestination and stuff there.</li></ul>

Modified: websites/production/cxf/content/roadmap.html
==============================================================================
--- websites/production/cxf/content/roadmap.html (original)
+++ websites/production/cxf/content/roadmap.html Thu Apr 11 15:48:01 2013
@@ -145,29 +145,31 @@ Apache CXF -- Roadmap
 <ul><li>SOAP/TCP support (GSoC project)</li><li>Better management capabilities</li><li>Better Acegi integration</li><li>Update to WS-RM 1.1</li><li>Enhancements to WS-Trust support</li></ul>
 
 
-<h2><a shape="rect" name="Roadmap-CXFversion2.4"></a>CXF version 2.4</h2>
+<h2><a shape="rect" name="Roadmap-CXFversion2.7.x"></a>CXF version 2.7.x</h2>
 
-<p>The CXF 2.4.x releases include bug fix releases for issues users encounter with 2.4.x versions.   These releases will be done on a branch by selectively merging fixes from the trunk on an as-needed basis.  For the most part, there would be fixes for:</p>
+<p>The CXF 2.7.x releases include bug fix releases for issues users encounter with 2.7.x versions.   These releases will be done on a branch by selectively merging fixes from the trunk on an as-needed basis.  For the most part, there would be fixes for:</p>
 <ul><li>Interopability issues</li><li>Critical show stoppers</li></ul>
 
 
-<p>Some new features may be back ported from trunk to provide some new functionality to users quicker if it doesn't affect the existing stuff or can enhance some of the new features in 2.4.  </p>
+<p>Some new features may be back ported from trunk to provide some new functionality to users quicker if it doesn't affect the existing stuff or can enhance some of the new features in 2.7.  </p>
 
-<p>See the <a shape="rect" href="http://cxf.apache.org/docs/24-migration-guide.html">2.4 Migration Guide</a> for more details about new features and changes.</p>
+<p>See the <a shape="rect" href="http://cxf.apache.org/docs/27-migration-guide.html">2.7 Migration Guide</a> for more details about new features and changes.</p>
 
 
-<h2><a shape="rect" name="Roadmap-CXFversion2.3.x"></a>CXF version 2.3.x</h2>
-<p>The CXF 2.3.x releases include bug fix releases for issues users encounter with 2.3.x versions.   These releases will be done on a branch by selectively merging fixes from the trunk on an as-needed basis.  For the most part, there would be fixes for:</p>
+<h2><a shape="rect" name="Roadmap-CXFversions2.6.x%2F2.5.x"></a>CXF versions 2.6.x/2.5.x</h2>
+<p>The CXF 2.6.x and 2.5.x releases include bug fix releases for issues users encounter with those versions.   These releases will be done on a branch by selectively merging fixes from the trunk on an as-needed basis.  For the most part, there would be fixes for:</p>
 <ul><li>Interopability issues</li><li>Critical show stoppers</li></ul>
 
 
-<p>Some new features may be back ported from trunk to provide some new functionality to users quicker if it doesn't affect the existing stuff or can enhance some of the new features in 2.3.  </p>
+<p>A few new features may be back ported from trunk to provide some new functionality to users quicker if it doesn't affect the existing stuff.  </p>
 
-<p>See the <a shape="rect" href="http://cxf.apache.org/docs/23-migration-guide.html">2.3 Migration Guide</a> for more details about new features and changes.</p>
+<p>See the <a shape="rect" href="http://cxf.apache.org/docs/26-migration-guide.html">2.6 Migration Guide</a> for more details about new features and changes.</p>
 
-<h2><a shape="rect" name="Roadmap-LegacyCXFversions2.2.x%2C2.1.x%2Cand2.0.xEOL"></a>Legacy CXF versions 2.2.x, 2.1.x, and 2.0.x - EOL</h2>
+<p>See the <a shape="rect" href="http://cxf.apache.org/docs/26-migration-guide.html">2.5 Migration Guide</a> for more details about new features and changes.</p>
 
-<p>2.2.12 was the last version of 2.2.x to be released at the ASF.  2.1.10 was the last version of 2.1.x to be released at ASF. 2.0.13 was the last version of 2.0.x to be released at ASF.  2.1.x and 2.0.x are now considered end-of-life and are therefore unsupported. Users are highly encouraged to <a shape="rect" href="http://cxf.apache.org/docs/migration-guides.html">migrate</a> to newer versions of CXF.</p>
+<h2><a shape="rect" name="Roadmap-LegacyCXFversions2.4.x%2C2.3.%2C2.2.x%2C2.1.x%2Cand2.0.xEOL"></a>Legacy CXF versions 2.4.x, 2.3., 2.2.x, 2.1.x, and 2.0.x - EOL</h2>
+
+<p>Versions of CXF prior to 2.5.x are no longer supported at Apache.  They are now considered end-of-life and are therefore unsupported. Users are highly encouraged to <a shape="rect" href="http://cxf.apache.org/docs/migration-guides.html">migrate</a> to newer versions of CXF.</p>