[jira] Commented: (AXIS2-4079) Namespace issue in SOAP message generated

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

    [ https://issues.apache.org/jira/browse/AXIS2-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639639#action_12639639 ] 

Krishna commented on AXIS2-4079:
--------------------------------

One more thing that I found is that, the generated XML is proper when using WoodStox.  But, I looked at the code and saw that Axis2 has a slightly different serialization logic if it finds WoodStox implementation than when it finds a beastax implementation.

> Namespace issue in SOAP message generated
> -----------------------------------------
>
>                 Key: AXIS2-4079
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4079
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windown XP, Sun JVM 1.5.0_10
>            Reporter: Krishna
>
> I am facing an issue with SOAP message generated by AXIS.
>  
> We have a SOAP request, which when we build and log it, gets logged as:
>  
> <OurService xmlns="http://www.somthing.com/ournamespace" xmlns:arr="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
>   <param1>
>     <arr:string>1</arr:string>
>     <arr:string>2</arr:string>
>   </param1>
>   <param2>ABC</param2>
> </OurService>
>  
> This is proper. But, when it is sent on the wire, it gets sent as:
>  
> <OurService xmlns="http://www.somthing.com/ournamespace">
>   <param1>
>     <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">1</string>
>     <string>2</string>
>   </param1>
>   <param2>ABC</param2>
> </OurService>
>  
> Note that the xmlns declaration for http://schemas.microsoft.com/2003/10/Serialization/Arrays happens only once - for the first child inside param1, instead of happening on each of them. 
>  
> I could trace it to OMSerializerUtil, where it is considering a namespace declaration generated at the sibling level as a namespace already written and hence need not be written again. 
> I already searched the net and the bugs in Axis and Axiom, but could not get to anything that resembles this behavior. So, logging it as a bug, as it looks like we have stumbled into an issue no one has probably faced before. 
>  

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org