Author: buildbot
Date: Wed Mar 28 16:48:04 2012
New Revision: 810431
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 28
16:48:04 2012
@@ -123,7 +123,7 @@ Apache CXF -- 2.6 Migration Guide
<div class="wiki-content">
<div id="ConfluenceContent"><h3><a shape="rect"
name="2.6MigrationGuide-NewFeatures"></a>New Features</h3>
-<ul><li>The big OSGi bundle used in the Karaf features.xml has been replaced
with the individual modules which are now all individual bundles. The big
OSGi bundle is still built, but some features may not be available if that is
used instead of the little bundles.</li><li>New ability to configure HTTP
Conduits from the OSGi config:admin service</li><li>New ability to configure
the CXF created HTTP Jetty ports from config:admin service</li><li>OAuth 2
support</li><li>STS updates to support Renew and Cancel as well as updates to
support more pluggable token validations.</li></ul>
+<ul><li>The big OSGi bundle used in the Karaf features.xml has been replaced
with the individual modules which are now all individual bundles. The big
OSGi bundle is still built, but some features may not be available if that is
used instead of the little bundles.</li><li>New ability to configure HTTP
Conduits from the OSGi config:admin service</li><li>New ability to configure
the CXF created HTTP Jetty ports from config:admin service</li><li>OAuth 2
support</li><li>The STS now supports the Renewal binding for SAML and
SecurityContextTokens.</li><li>The STS also supports bulk
issuing/validation/cancelling/renewal of security tokens.</li><li>The STS
supports some advanced features based around Claims, such as Claims
Transformation, and pluggable custom Claims Parsing.</li><li>The WS-Security
module now supports replay detection by default of Timestamps and UsernameToken
nonces.</li></ul>
<h3><a shape="rect" name="2.6MigrationGuide-RemovedModules"></a>Removed
Modules</h3>
@@ -140,7 +140,7 @@ Apache CXF -- 2.6 Migration Guide
<h3><a shape="rect" name="2.6MigrationGuide-DependencyChanges"></a>Dependency
Changes</h3>
-<ul><li>The org.apache.cxf.tools.* classes that were in cxf-api have been
moved into cxf-tools-common or cxf-tools-validator.</li><li>The
org.apache.cxf.ws.policy classes that were in cxf-api have been moved into
cxf-rt-ws-policy.</li><li>cxf-common-utilities is no longer available. All the
classes in there were moved into cxf-api to represent a complete
"api".</li><li>Various classes in cxf-rt-core and cxf-rt-ws-addr have been
moved up to cxf-api to resolve split-package issues. Dependencies on
cxf-rt-core would have transitively brought in cxf-api anyway, so there should
be little impact.</li><li>Spring is now an optional component of the http-jetty
transports module and other modules. Applications that may have pulled in
Spring transitively via CXF will be required to declare required spring
dependencies in their own poms directly.</li><li>Most of the optional JAX-RS
Providers have been moved out of the cxf-rt-frontend-jaxrs module and into a
cxf-rt-rs-extension-provi
ders module with the various dependencies marked optional/provided.
Applications that use these optional providers will need to add the required
dependencies. Also, the package names of many of those providers has changed to
resolve split-package issues. Example:
org.apache.cxf.jaxrs.provider.JSONProvider ->
org.apache.cxf.jaxrs.provider.json.JSONProvider</li></ul>
+<ul><li>The org.apache.cxf.tools.* classes that were in cxf-api have been
moved into cxf-tools-common or cxf-tools-validator.</li><li>The
org.apache.cxf.ws.policy classes that were in cxf-api have been moved into
cxf-rt-ws-policy.</li><li>cxf-common-utilities is no longer available. All the
classes in there were moved into cxf-api to represent a complete
"api".</li><li>Various classes in cxf-rt-core and cxf-rt-ws-addr have been
moved up to cxf-api to resolve split-package issues. Dependencies on
cxf-rt-core would have transitively brought in cxf-api anyway, so there should
be little impact.</li><li>Spring is now an optional component of the http-jetty
transports module and other modules. Applications that may have pulled in
Spring transitively via CXF will be required to declare required spring
dependencies in their own poms directly.</li><li>Most of the optional JAX-RS
Providers have been moved out of the cxf-rt-frontend-jaxrs module and into a
cxf-rt-rs-extension-provi
ders module with the various dependencies marked optional/provided.
Applications that use these optional providers will need to add the required
dependencies. Also, the package names of many of those providers has changed to
resolve split-package issues. Example:
org.apache.cxf.jaxrs.provider.JSONProvider ->
org.apache.cxf.jaxrs.provider.json.JSONProvider</li><li>EhCache is now a
compile time dependency of the cxf-rt-ws-security module to support caching and
replay detection. It can be safely excluded downstream, at the expense of
weakening the caching support.</li></ul>
