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

Andreas Veithen resolved WSCOMMONS-530.
---------------------------------------

    Fix Version/s: Axiom 1.2.9
       Resolution: Fixed

This should be fixed in the latest trunk. Thanks for reporting this issue.

> AXIOM DOM implementation of SOAPFaultDetailImpl only serializes the first 
> child node whereas the LLOM implementation serializes all children
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WSCOMMONS-530
>                 URL: https://issues.apache.org/jira/browse/WSCOMMONS-530
>             Project: WS-Commons
>          Issue Type: Bug
>          Components: AXIOM
>    Affects Versions: Axiom 1.2.8
>            Reporter: Dave Bryant
>            Assignee: Andreas Veithen
>             Fix For: Axiom 1.2.9
>
>
> The SOAPFaultDetailImpl.internalSerialize() and 
> SOAP11FaultDetailImpl.internalSerialize() methods in the AXIOM DOM 
> implementation only serialize the first child of the fault details element.  
> This is inconsistent both with the LLOM implementation which serializes all 
> children, and would appear to be inconsistent with section 4.1.4 of the WS-I 
> basic profile which states "A RECEIVER MUST accept fault messages that have 
> any number of elements, including zero, appearing as children of the detail 
> element. Such children can be qualified or unqualified." 
> (http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16438576).
> Furthermore, this can cause problems even with a single child element of the 
> fault details element if there was any whitespace in the original serialized 
> XML.  If there was whitespace between the details element and the first 
> element child then only the whitespace child is serialized on output.

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