cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Jain (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CXF-6708) Conflicting class org.apache.cxf.configuration.spring.StringBeanDefinitionParser
Date Mon, 14 Dec 2015 12:51:46 GMT

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

Rohit Jain edited comment on CXF-6708 at 12/14/15 12:50 PM:
------------------------------------------------------------

compare the class StringBeanDefinitionParser in cxf-bundle-2.7.18 (the latest release version)
and the one in cxf-core 3.0.3.
They are different on line 12.. Ideally should be same. If we need to use both these artifacts
then its not possible.
Since the class org.apache.cxf.wsdl11.WSDLServiceFactoryImpl (required for stubbing) is present
in cxf-bundle..and not in core..
So if we use cxf-bundle along with cxf-core then the mentioned conflicting class creates a
problem. And if we dont use cxf-core then we cant use upgraded spring security artifacts,since
the bundle doesnt have call to the method addConstructorArgValue() in StringBeanDefinitionParser's
  doParse() method


was (Author: hchikhal):
compare the class StringBeanDefinitionParser in cxf-bundle-2.7.18 (the latest release version)
and the one in cxf-core 3.0.3.
They are different on line 12.. Ideally should be same. If we need to use both these artifacts
then its not possible.
Since the class org.apache.cxf.wsdl11.WSDLServiceFactoryImpl (required for stubbing) is present
in cxf-bundle..and not in core..
So if we use cxf-bundle then the mentioned conflicting class creates a problem. And if we
dont use cxf-core then we cant use upgraded spring security artifacts

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

Mime
View raw message