You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Scott Parkerson (JIRA)" <ji...@apache.org> on 2012/04/30 15:56:47 UTC
[jira] [Created] (CXF-4278) Karaf features.xml for CXF wants to
load EhCache for cxf-sts-ws and cxf-ws-security
Scott Parkerson created CXF-4278:
------------------------------------
Summary: 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, 2.6.1
Environment: Apache Karaf 2.2.6 + Felix OSGi Container
Reporter: Scott Parkerson
Priority: Minor
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
[jira] [Commented] (CXF-4278) Karaf features.xml for CXF wants to
load EhCache for cxf-sts-ws and cxf-ws-security
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269423#comment-13269423 ]
Freeman Fang commented on CXF-4278:
-----------------------------------
add the ehcache bundle back
http://svn.apache.org/viewvc?rev=1334892&view=rev
> 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
[jira] [Resolved] (CXF-4278) Karaf features.xml for CXF wants to
load EhCache for cxf-sts-ws and cxf-ws-security
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved CXF-4278.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.6.1
commit fix
http://svn.apache.org/viewvc?rev=1334891&view=rev
> 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, 2.6.1
> 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
[jira] [Updated] (CXF-4278) Karaf features.xml for CXF wants to
load EhCache for cxf-sts-ws and cxf-ws-security
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang updated CXF-4278:
------------------------------
Affects Version/s: (was: 2.6.1)
> 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
[jira] [Assigned] (CXF-4278) Karaf features.xml for CXF wants to
load EhCache for cxf-sts-ws and cxf-ws-security
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang reassigned CXF-4278:
---------------------------------
Assignee: Freeman Fang
> 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, 2.6.1
> Environment: Apache Karaf 2.2.6 + Felix OSGi Container
> Reporter: Scott Parkerson
> Assignee: Freeman Fang
> Priority: Minor
>
> 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
[jira] [Commented] (CXF-4278) Karaf features.xml for CXF wants to
load EhCache for cxf-sts-ws and cxf-ws-security
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269407#comment-13269407 ]
Freeman Fang commented on CXF-4278:
-----------------------------------
Hi Scott,
Just want to clarify, installing higher version of ehcache won't prevent you to install lower version of ehcache. Even though you have ehcache bundle from cxf features, let's say the version is [2.5, ...), you still can install another ehcache bundle which version range meet the Hibernate requirement, multiple version of same lib can co-exist in OSGi container is big benefit by OSGi nature.
Back to this issue, yeah, I think we should remove ehcache bundle from cxf feature as it's compile time necessary only, we may also need add version range for the optional import net.sf.ehcache(likely [2.5.0, 3.0.0) in CXF to prevent it load some incompatible older net.sf.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, 2.6.1
> Environment: Apache Karaf 2.2.6 + Felix OSGi Container
> Reporter: Scott Parkerson
> Assignee: Freeman Fang
> Priority: Minor
>
> 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
[jira] [Commented] (CXF-4278) Karaf features.xml for CXF wants to
load EhCache for cxf-sts-ws and cxf-ws-security
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ 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