cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Jain (JIRA)" <>
Subject [jira] [Commented] (CXF-6708) Conflicting class org.apache.cxf.configuration.spring.StringBeanDefinitionParser
Date Tue, 15 Dec 2015 07:30:46 GMT


Rohit Jain commented on CXF-6708:

I am using cxf-bundle 2.7.18 since there is no upgraded release version of cxf 3.0.3 which
supports upgraded Spring beans artifacts(4.0.3).
cxf-bundle has a milestone release which supports this but then we should not be using milestone
versions for our production releases.

In simpler words is there any release version of cxf-bundle that has with the below method?

protected void doParse(Element element, BeanDefinitionBuilder builder)

If yes kindly let me know the cxf-bundle release version that supports the addConstructorArgValue
of upgraded Spring artifacts

> Conflicting class org.apache.cxf.configuration.spring.StringBeanDefinitionParser
> --------------------------------------------------------------------------------
>                 Key: CXF-6708
>                 URL:
>             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
> cxf should make these method calls consistent to cope up with upgraded spring security
> Don't understand why this was missed.

This message was sent by Atlassian JIRA

View raw message