cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r865676 - in /websites/production/cxf/content: cache/docs.pageCache docs/30-migration-guide.html
Date Fri, 14 Jun 2013 17:47:56 GMT
Author: buildbot
Date: Fri Jun 14 17:47:56 2013
New Revision: 865676

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 Fri Jun 14 17:47:56 2013
@@ -131,10 +131,6 @@ Apache CXF -- 3.0 Migration Guide
 <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>Remove QueryHandlers -&gt; these were originally used for the ?wsdl
processing (and is still used for ?js).  However, that stuff is better done directly on the
interceptor chains as interceptors to allow user supplied interceptors to also handle them.
  I'd like to just remove these.  (obviously update the ?js stuff)  Would simplify the CXFServlet
a bit.</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>
 
 
@@ -147,9 +143,6 @@ Apache CXF -- 3.0 Migration Guide
 <ul><li>Move feature impls out of API and into core. Currently feature and interceptor
classes are in different packages. Which makes it difficult to modularize them. So we should
rather have one package per feature where feature class and interceptor classes are located</li></ul>
 
 
-<ul><li>Make AbstractFeature subclass WebServiceFeature and update the JAX-WS
frontend to look for them.</li></ul>
-
-
 <ul><li>Add new code generator frontend to add CXF specific constructors and
methods.</li></ul>
 
 
@@ -172,6 +165,16 @@ Apache CXF -- 3.0 Migration Guide
 
 
 <ul><li>Dropped support for Karaf 2.2.x.  Karaf 2.3.x is now required.</li></ul>
+
+
+<ul><li>Make AbstractFeature subclass WebServiceFeature and update the JAX-WS
frontend to look for them.</li></ul>
+
+
+<ul><li>Remove QueryHandlers -&gt; these were originally used for the ?wsdl
processing (and is still used for ?js).  However, that stuff is better done directly on the
interceptor chains as interceptors to allow user supplied interceptors to also handle them.
  I'd like to just remove these.  (obviously update the ?js stuff)  Would simplify the CXFServlet
a bit.</li></ul>
+
+
+<ul><li>Removed all the /META-INF/cxf/cxf-extension-XYZ.xml files.  They have
been deprecated an not needed for a long time.</li></ul>
+
 </div>
            </div>
            <!-- Content -->



Mime
View raw message