You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Aki Yoshida (JIRA)" <ji...@apache.org> on 2013/07/16 15:52:49 UTC
[jira] [Resolved] (CXF-4577) Support EHCACHE 2.5.2+
[ https://issues.apache.org/jira/browse/CXF-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aki Yoshida resolved CXF-4577.
------------------------------
Resolution: Fixed
Fix Version/s: 2.7.6
2.6.9
2.5.11
changed the code to assign the right creation method for cache manager creation.
if the new method is available, it is used. otherwise, the old method is used.
> Support EHCACHE 2.5.2+
> -----------------------
>
> Key: CXF-4577
> URL: https://issues.apache.org/jira/browse/CXF-4577
> Project: CXF
> Issue Type: Improvement
> Components: JAX-WS Runtime
> Affects Versions: 2.7.0
> Reporter: Jason Pell
> Priority: Minor
> Fix For: 2.5.11, 2.6.9, 2.7.6
>
> Attachments: EhCacheIssue.tar.gz
>
>
> Upgrading ehcache to 2.5.2 causes some unexpected issues when using ws-security timestamp ehcache and / or nonce caches. Due to an api change in 2.5.2 when destroying an endpoint the global ehcache CacheManager is also shutdown.
> I am attaching a project which demonstrates the issue. I will be working on a fix for the issue so we can upgrade to 2.5.2. The fix will be backwards compatible to 2.5.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira