cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hrishikesh Chikhale (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CXF-6708) Conflicting class org.apache.cxf.configuration.spring.StringBeanDefinitionParser
Date Mon, 14 Dec 2015 10:52:46 GMT
Hrishikesh Chikhale created CXF-6708:
----------------------------------------

             Summary: 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: Hrishikesh Chikhale
            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)

Mime
View raw message