Author: buildbot
Date: Tue Nov 11 14:46:50 2014
New Revision: 928771
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/31-migration-guide.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/docs/31-migration-guide.html
==============================================================================
--- websites/production/cxf/content/docs/31-migration-guide.html (original)
+++ websites/production/cxf/content/docs/31-migration-guide.html Tue Nov 11
14:46:50 2014
@@ -107,7 +107,7 @@ Apache CXF -- 3.1 Migration Guide
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><h3 id="id-3.1MigrationGuide-MajorNotes">Major
Notes</h3><ul><li>CXF 3.1 no longer supports Java 6.   You must use Java 7
or Java 8.</li><li>The JAX-WS/Simple frontend ServerFactoryBean will
automatically call reset at the end of the create() call.   This allows
resources to be cleaned up and garbage collected sooner.  However, it also
prevents multiple calls to create() from sharing the same
ServerInfo/EndpointInfo/etc... objects like they would we 3.0.x.   That
sharing has caused many problems in the past due to sharing of properties (like
token caches) that are stored on those objects so the new behavior is more
"correct", but it is different than previous versions so care must be taken
while upgrading.</li><li>The Karaf features.xml file for CXF 3.1 no longer will
install spring or spring-dm when installing the "cxf" feature.  If you
require spring/spring-dm, you will need to install those features prior to
installing the CXF
feature.</li></ul><p> </p><h3 id="id-3.1MigrationGuide-NewFeatures">New
Features</h3><p> </p><p> </p><h3
id="id-3.1MigrationGuide-MajorDependencyChanges">Major Dependency
Changes</h3><ul><li>The Jetty based HTTP transport has been updated to support
Jetty 9 as well as Jetty 8.   However, support for Jetty 7 has been
dropped.</li><li>Due to the Jetty upgrade, support for running Jetty based
endpoints in Karaf 2.3.x has been dropped.</li><li>Support for using JAX-WS 2.1
based API jars has been removed.  Java 7 (now required) includes JAX-WS
2.2 so this should not be an issue.</li></ul></div>
+<div id="ConfluenceContent"><h3 id="id-3.1MigrationGuide-MajorNotes">Major
Notes</h3><ul><li>CXF 3.1 no longer supports Java 6.   You must use Java 7
or Java 8.</li><li>The JAX-WS/Simple frontend ServerFactoryBean will
automatically call reset at the end of the create() call.   This allows
resources to be cleaned up and garbage collected sooner.  However, it also
prevents multiple calls to create() from sharing the same
ServerInfo/EndpointInfo/etc... objects like they would we 3.0.x.   That
sharing has caused many problems in the past due to sharing of properties (like
token caches) that are stored on those objects so the new behavior is more
"correct", but it is different than previous versions so care must be taken
while upgrading.</li><li>The Karaf features.xml file for CXF 3.1 no longer will
install spring or spring-dm when installing the "cxf" feature.  If you
require spring/spring-dm, you will need to install those features prior to
installing the CXF
feature.</li><li>The STS (Security Token Service) now issues tokens using the
RSA-SHA256 signature algorithm by default (previously RSA-SHA1), and the
SHA-256 digest algorithm (previously SHA-1).</li></ul><p> </p><h3
id="id-3.1MigrationGuide-NewFeatures">New
Features</h3><p> </p><p> </p><h3
id="id-3.1MigrationGuide-MajorDependencyChanges">Major Dependency
Changes</h3><ul><li>The Jetty based HTTP transport has been updated to support
Jetty 9 as well as Jetty 8.   However, support for Jetty 7 has been
dropped.</li><li>Due to the Jetty upgrade, support for running Jetty based
endpoints in Karaf 2.3.x has been dropped.</li><li>Support for using JAX-WS 2.1
based API jars has been removed.  Java 7 (now required) includes JAX-WS
2.2 so this should not be an issue.</li></ul></div>
</div>
<!-- Content -->
</td>
