[ 
https://issues.apache.org/jira/browse/CXF-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058175#comment-15058175
 ] 

Rohit Jain commented on CXF-6708:
---------------------------------

In addition to this I forgot to mention that my application is using a cxf class
org.apache.cxf.wsdl.WSDLServiceFactory which was being called internally in the 
wsdl2java phase of maven cxf-codegen-plugin

However earlier this class was present in cxf-bundle which I am no longer using.
Found that apart from cxf-bundle it is present in cxf-rt-core and whose latest 
version is 2.7.18. I could not find any other artifact of cxf with version 
3.0.3 that uses this.If you can let me know any cxf 3.0.3 version artifact that 
has this class, it would be really helpful. Thanks in advance

> 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)

Reply via email to