[
https://issues.apache.org/jira/browse/CXF-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057996#comment-15057996
]
Daniel Kulp commented on CXF-6708:
----------------------------------
Use of cxf-bundle has been deprecated from 2.5 and removed starting in 3.0.
You need to use the individual modules that you need for your application. (or
grab the pom from 2.7 and roll your own uber bundle, but that no longer has
been tested)
> 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
> Priority: Blocker
>
> 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)
