[
https://issues.apache.org/jira/browse/CXF-6461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585303#comment-14585303
]
John D. Ament commented on CXF-6461:
------------------------------------
Actually, I spent a lot of time trying to figure out why this wasn't working
for me. Then it dawned on me to check spring versions. So, yes, what I put in
the ticket is incorrect. Spring is properly checked on the classpath, however
there are some compatibility issues.
My app does package spring, but not by my own choice (it comes from one of our
internal libraries that brings in all of spring, even though most of its not
used). For deployment reasons, the whole thing ends up there. In CXF 2.7,
you're depending on Spring 3.0.7 which happens to be what I'm pointing to. CXF
3 is using Spring 3.2, which is not compatible. The check on load is checking
for classes, however there are method differences between the two. It looks
like in my app currently, I am using Spring's AOP support. So, would it be
worth extending the spring check to also check for method existence?
> Smarter deactivation of SpringAopClassHelper
> --------------------------------------------
>
> Key: CXF-6461
> URL: https://issues.apache.org/jira/browse/CXF-6461
> Project: CXF
> Issue Type: Improvement
> Components: Tooling
> Affects Versions: 3.0.5
> Reporter: John D. Ament
>
> Improve how ClassHelper activates Spring or default implementation.
> https://github.com/apache/cxf/blob/3.0.x-fixes/core/src/main/java/org/apache/cxf/common/util/ClassHelper.java#L40
> Instead of relying solely on the JVM flag, also check for spring on the
> classpath.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
