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

Deepal Jayasinghe reassigned AXIS2-4339:
----------------------------------------

    Assignee: Amila Chinthaka Suriarachchi

> xmlns not declared in web service response element
> --------------------------------------------------
>
>                 Key: AXIS2-4339
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4339
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: adb
>    Affects Versions: 1.4.1
>            Reporter: Felipe Carvalho
>            Assignee: Amila Chinthaka Suriarachchi
>         Attachments: wsdl.xml
>
>
> The deserializing logic seems not be working totally correctly for null 
> attributes.
> For some reason, the xmlns is not declared for all elements that have 
> xsi:nil="true", which harms the service interoperability with .Net, for 
> instance. When using Java clients, there's no problem, but .Net clients get 
> an error message saying "System.Xml.XmlException: 'xsi' is an undeclared 
> namespace".
> Below is an example of such response XML:
> <?xml version='1.0' encoding='utf-8'?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>   <soapenv:Body>
>     <ns:recuperarTiposBiotaResponse xmlns:ns="http://endpoint.sma.com.br";>
>       <ns:return      
>               xmlns:ax217="http://retorno.to.endpoint.sma.com.br/xsd";
>               xmlns:ax215="http://requisicao.to.endpoint.sma.com.br/xsd"; 
>               xmlns:ax218="http://to.endpoint.sma.com.br/xsd"; 
> type="br.com.sma.endpoint.to.retorno.RetornoTipoBiota">
>         <ax217:error xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
> xsi:nil="true"></ax217:erro>
>         <ax217:tipos xsi:nil="true"></ax217:tipos>
>       </ns:return>
>     </ns:recuperarTiposBiotaResponse>
>   </soapenv:Body>
> </soapenv:Envelope>

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