[
https://issues.apache.org/jira/browse/CXF-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-6708.
------------------------------
Resolution: Invalid
Assignee: Daniel Kulp
Fix Version/s: Invalid
This is a mix of CXF versions (unsupported) and versions of Spring that are not
supported by the older version of CXF (which is also now unsupported). Please
make sure everything gets updated to CXF 3.0.x or newer (preferably 3.1.x).
> Conflicting class
> org.apache.cxf.configuration.spring.StringBeanDefinitionParser
> --------------------------------------------------------------------------------
>
> Key: CXF-6708
> URL: https://issues.apache.org/jira/browse/CXF-6708
> Project: CXF
> Issue Type: Bug
> Components: Build system
> Reporter: Rohit Jain
> Assignee: Daniel Kulp
> Priority: Blocker
> Fix For: Invalid
>
>
> We have upgraded Spring Security to 4.0.3. However we see that cxf-api and
> cxf bundle is not upgraded to use it.
> cxf-core is upgraded to support Spring Security
> However we require cxf-core as well as cxf-bundle(for cxf stubbing wsdl2Java)
> The issue is that StringBeanDefinitionParser is present in both the these
> jars with same package name and contents. with one major difference
> StringBeanDefinitionParser in cxf-core has below line
> builder.addConstructorArgValue(DOMUtils.getRawContent(element));
> StringBeanDefinitionParser in cxf-bundle has below line
> builder.addConstructorArg(DOMUtils.getRawContent(element));
> Always the StringBeanDefinitionParser in cxf-bindle takes precedence and the
> war deployment fails.
> cxf should make these method calls consistent to cope up with upgraded spring
> security version
> Don't understand why this was missed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
