Author: buildbot
Date: Tue Nov 19 17:47:57 2013
New Revision: 887253
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 Tue Nov 19
17:47:57 2013
@@ -122,48 +122,64 @@ 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 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 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>
+<h4><a shape="rect" name="3.0MigrationGuide-JAXRS"></a>JAX-RS</h4>
+<ul><li>JAX-RS 2.0 has been completely implemented.</li></ul>
+
+
+<ul><li>JAX-RS WADL auto-generation code has been moved to a new
cxf-rt-rs-service-description module.</li></ul>
+
+
+<ul><li>JAX-RS 2.0 Client API and CXF specific WebClient and Proxy client code
is now available in a new cxf-rt-rs-client module. Important: the namespace for
jaxrs:client elements has changed from "http://cxf.apache.org/jaxrs"; to
"http://cxf.apache.org/jaxrs-client";</li></ul>
+
+
+<ul><li>Bean Validation 1.1 is supported for all CXF frontends</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>
+<h4><a shape="rect" name="3.0MigrationGuide-JAXWS%2FSoap"></a>JAX-WS/Soap</h4>
-<ul><li>Go through all the @Deprecated things and remove them. Likewise,
remove unused method params (I know there are a couple on the Destination API)
and such.</li></ul>
+<ul><li>Add new code generator frontend to add CXF specific constructors and
methods. (pass "-fe cxf" to wsdl2java)</li></ul>
-<ul><li>POSSIBLY update various API's to pass in the Bus (or other objects) if
needed instead of holding it as an instance variable. That would allow
singleton instances for things like the transports and such. For example, it
would be good to register a "FooCXFTransport" as an OSGi service that we could
lookup later. Right now, we couldn't do that unless you only used a global
bus, which isn't exactly what the purpose of the Bus is.</li></ul>
+<ul><li>Make AbstractFeature subclass WebServiceFeature and update the JAX-WS
frontend to look for them.</li></ul>
-<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>"jaxb-validation-event-handler"s now apply for both Reading and
Writing. (previously only applied to Reading). There are separate
jaxb-(reader|writer)-validation-event-handler properties if you need it set for
only one direction.</li></ul>
-<ul><li>Add new code generator frontend to add CXF specific constructors and
methods.</li></ul>
+<h4><a shape="rect" name="3.0MigrationGuide-WSSecurity"></a>WS-Security</h4>
+<h4><a shape="rect"
name="3.0MigrationGuide-WSReliableMessaging"></a>WS-ReliableMessaging</h4>
-<h3><a shape="rect" name="3.0MigrationGuide-Workfinished"></a>Work
finished</h3>
+<h4><a shape="rect" name="3.0MigrationGuide-CXFModule%2FJarChanges"></a>CXF
Module/Jar Changes</h4>
<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>
+<ul><li>Dropped support for Karaf 2.2.x. Karaf 2.3.x is now
required.</li></ul>
-<ul><li>The unused "run()" method on Bus was removed.</li></ul>
+<ul><li>The direct dependency on a javax.mail implementation has been removed
and the CXF maven poms will not pull one in transitively anymore. For MOST
users, this is not a problem. However, if your application uses MTOM or Soap
w/Attachments or similar that requires some of the DataContentHandlers that are
part of the mail implementations, you may need to re-add this to your
classpath.</li></ul>
-<ul><li>Merge BaseDataReader/DataReader and the same for the writer getting
rid of the "Base" versions that are unreferenced.</li></ul>
+<ul><li>DynamicClientFactory was moved from the JAXB databinding to the Simple
frontend. However, users are strongly encouraged to use the
JaxWsDynamicClientFactory subclass.</li></ul>
-<ul><li>The 2 unused params on Destination.getBackChannel were removed. They
were unused and normally passed in as null.</li></ul>
+<h4><a shape="rect"
name="3.0MigrationGuide-Removed%2FChangedAPI%27s"></a>Removed/Changed API's</h4>
-<ul><li>Dropped support for Karaf 2.2.x. Karaf 2.3.x is now
required.</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>
-<ul><li>Make AbstractFeature subclass WebServiceFeature and update the JAX-WS
frontend to look for them.</li></ul>
+<ul><li>The unused "run()" method on Bus was removed.</li></ul>
+
+
+<ul><li>Merge BaseDataReader/DataReader and the same for the writer getting
rid of the "Base" versions that are unreferenced.</li></ul>
+
+
+<ul><li>The 2 unused params on Destination.getBackChannel were removed. They
were unused and normally passed in as null.</li></ul>
<ul><li>Remove QueryHandlers -> 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>
@@ -187,12 +203,6 @@ Apache CXF -- 3.0 Migration Guide
<ul><li>Many of our interfaces/classes that held onto constants were either
removed or moved. In particular XmlSchemaConstants was removed (use the
Constants from the XmlSchema library directly), WSDLConstants was moved from
api to rt-wsdl, SOAPConstants was removed (most are available in
WSDLConstants). Goal is to reduce some memory usage and help startup time and
reduce a lot of duplication.</li></ul>
-<ul><li>The direct dependency on a javax.mail implementation has been removed
and the CXF maven poms will not pull one in transitively anymore. For MOST
users, this is not a problem. However, if your application uses MTOM or Soap
w/Attachments or similar that requires some of the DataContentHandlers that are
part of the mail implementations, you may need to re-add this to your
classpath.</li></ul>
-
-
-<ul><li>DynamicClientFactory was moved from the JAXB databinding to the Simple
frontend. However, users are strongly encouraged to use the
JaxWsDynamicClientFactory subclass.</li></ul>
-
-
<ul><li>AlternativeSelector and the PolicyEngine and other PolicyRelated
classes have been updated to pass the current Message in (when appropriate) to
allow using message contextual information to select the alternative. HOWEVER,
keep in mind that the selected alternative is likely cached and thus if
contextual information changes, the alternatively may not be
recalculated.</li></ul>
@@ -201,17 +211,6 @@ Apache CXF -- 3.0 Migration Guide
<ul><li>ServletController will not override the endpoint addresses by default
as it has side-effects when a given endpoint is accessed via multiple paths.
Set CXFServlet "disable-address-updates" parameter to 'false' if
required.</li></ul>
-
-<ul><li>JAX-RS 2.0 has been completely implemented.</li></ul>
-
-
-<ul><li>JAX-RS WADL auto-generation code has been moved to a new
cxf-rt-rs-service-description module.</li></ul>
-
-
-<ul><li>JAX-RS 2.0 Client API and CXF specific WebClient and Proxy client code
is now available in a new cxf-rt-rs-client module. Important: the namespace for
jaxrs:client elements has changed from "http://cxf.apache.org/jaxrs"; to
"http://cxf.apache.org/jaxrs-client";</li></ul>
-
-
-<ul><li>Bean Validation 1.1 is supported for all CXF frontends</li></ul>
</div>
</div>
<!-- Content -->
