You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cxf.apache.org by bu...@apache.org on 2012/03/29 12:48:14 UTC
svn commit: r810533 - in /websites/production/cxf/content:
cache/docs.pageCache docs/26-migration-guide.html
Author: buildbot
Date: Thu Mar 29 10:48:14 2012
New Revision: 810533
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 Thu Mar 29 10:48:14 2012
@@ -146,6 +146,11 @@ Apache CXF -- 2.6 Migration Guide
<h3><a shape="rect" name="2.6MigrationGuide-RuntimeChanges"></a>Runtime Changes</h3>
<ul><li>The syntax of WS-SecurityPolicy policies is enforced more strictly. Some policies that worked with CXF < 2.6 will not load in CXF 2.6 as a result.</li><li>JMS Transport - when using TextMessage, CXF now leaves the contents as a String and uses java.io.Reader and java.io.Writer to boost performance. Previously, CXF would convert the Strings to/from byte[] requiring use of encoders, increasing memory usage, etc... However, some interceptors and functionality in CXF (or user interceptors) may expect or require they InputStream/OutputStreams, not Reader/Writer. In those cases, you may need to change to use a BytesMessage. For example, the FastInfoset feature and GZIP features expect to work on InputStream/OutputStream and thus would now work with TextMessage.</li></ul>
+
+
+
+<h4><a shape="rect" name="2.6MigrationGuide-SecurityCachingChanges"></a>Security Caching Changes</h4>
+<ul><li>EhCache is now used by default to cache SecurityTokens for re-use, and for replay detection. It is possible to plug in other implementations by configuration.</li><li>The WS-Security module now supports replay detection by default of Timestamps and UsernameToken nonces. The default caching time is 60 minutes.</li></ul>
</div>
</div>
<!-- Content -->