[
https://issues.apache.org/jira/browse/CXF-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269422#comment-13269422
]
Freeman Fang commented on CXF-4278:
-----------------------------------
Hi Scott,
Re-think about it, we need the ehcache bundle actually, without it, it will
weaken the caching support.
I just add the optional import net.sf.ehcache version range.
As I said before, installing higher version of ehcache won't prevent you to
install lower version of ehcache.
Freeman
> Karaf features.xml for CXF wants to load EhCache for cxf-sts-ws and
> cxf-ws-security
> -----------------------------------------------------------------------------------
>
> Key: CXF-4278
> URL: https://issues.apache.org/jira/browse/CXF-4278
> Project: CXF
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 2.6
> Environment: Apache Karaf 2.2.6 + Felix OSGi Container
> Reporter: Scott Parkerson
> Assignee: Freeman Fang
> Priority: Minor
> Fix For: 2.6.1
>
>
> According to the [migration
> guide|http://cxf.apache.org/docs/26-migration-guide.html]:
> {quote}
> 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.
> {quote}
> If that is the case, then why force a user to load a specific version of
> EhCache in the features.xml file for CXF? This breaks cases where, for
> instance, a user wants to use an EhCache compatible with old-school Hibernate
> (3.3.2) which requires net.sf.ehcache;version=[1.2.3, 2.0.0).
> Furthermore, it appears that there is no version bounding on the optional
> import of net.sf.ehcache in cxf-ws-security, so theoretically, my
> already-loaded version of EhCache should work just fine with CXF. :D
> Note: Setting this to a minor issue as it can be worked around by installing
> the features with {{--no-clean}} in Karaf and then removing the EhCache
> provided by CXF's features.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
