[jira] Resolved: (SMXCOMP-479) xsd namespace not brought forward in the soap response if using cxf-bc-provider. xsi namespace appears incorrectly as "xmlns:xsi=xsi" in soap envelope.

["Freeman Fang (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/SMXCOMP-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Freeman Fang resolved SMXCOMP-479.
----------------------------------

    Fix Version/s: servicemix-cxf-bc-2010.02
       Resolution: Fixed

The fix for SMXCOMP-759 also resolve this issue

> xsd namespace not brought forward in the soap response if using cxf-bc-provider.  xsi namespace appears incorrectly as "xmlns:xsi=xsi" in soap envelope.
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SMXCOMP-479
>                 URL: https://issues.apache.org/activemq/browse/SMXCOMP-479
>             Project: ServiceMix Components
>          Issue Type: Bug
>          Components: servicemix-cxf-bc
>    Affects Versions: 3.2.3, servicemix-cxf-bc-2008.01
>         Environment: WinXP professional,  External Web Service created using Axis 1.2 hosted on an IBM Websphere instance
>            Reporter: angelo angeles
>            Assignee: Freeman Fang
>             Fix For: servicemix-cxf-bc-2010.02
>
>
> Given thise use case:
> http:soap-consumer -> camel > cxf-provider-bc > external service
> The body of the soap response is returned as expected however the namespace for xmlns:xsd is missing in the soap envelope.  The namespace for schema instance also appears as "xmlns:xsi=xsi".  If an http:soap-provider is used then the xsd and xsi namespaces are brought correctly in the soap response.
> I was also looking at JbiInWsdl1Interceptor and there was a code portion that adds the xsi and xsd namespaces to the root element inside handleMessage() if useJbiWrapper is passed as true.  However, this particular method call below always returns null for me which forces the handleMessage() to exit and not have any of the namespace changes applied.  
> Element body = getBodyElement(message);
> if (body == null) {            
>     return;
> }
> Since I'm getting a soap response I'm assuming that some other interceptors were invoked afterwards but I'm not sure which.  Using tcpmon between the cxf-bc-provider and the external web service shows that the response generated by the external web service contains the xsd and xsi namespace definitions.

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