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

Josh Cummings commented on CXF-2752:
------------------------------------

It's looks like we may have found it.

I haven't dug very deep, but we were excluding wstx-asl in our pom in order to 
trim dependencies.  This worked fine in past versions, but it looks like we 
need to remove the exclusion to upgrade.

Sorry for the false alarm--thanks for looking into it all the same.

> Regression - CXF Client Spring Context Fails
> --------------------------------------------
>
>                 Key: CXF-2752
>                 URL: https://issues.apache.org/jira/browse/CXF-2752
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS, JAX-WS Runtime
>    Affects Versions: 2.2.7
>            Reporter: Josh Cummings
>
> In upgrading to 2.2.7, we found that our cxf client's spring configuration 
> would fail on startup with a NAMESPACE_ERR thrown from the writer.
> To reproduce, we simply include the following snippet in our client 
> application context:
> <bean id="client" factory-bean="clientFactory" factory-method="create" 
> lazy-init="false"/>
>       
> <bean id="clientFactory" class="org.apache.cxf.jaxws.JaxWsClientFactoryBean" 
> lazy-init="false">
>       <property name="address" value="http://localhost:8180"/>
>       <property name="serviceClass" value="org.my.project.MyService"/>
> </bean>
> It will fail when it tries to load cxf.xml using the 
> ControlledValidationXmlBeanDefinitionReader.
> It appears to occur because the namespace attributes are handed off by 
> W3CDomStreamWriter.writeAttribute with a namespaceURI of null instead of 
> their actual namespace.  It seems that either that method isn't the right 
> place to handle namespace attributes, meaning changing something upstream, or 
> that there is a bug in it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to