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

Aki Yoshida resolved CXF-4723.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.7.2
                   2.6.5
                   2.5.8
    
> stax outTransform may generate duplicate namespace declarations for global 
> attributes
> -------------------------------------------------------------------------------------
>
>                 Key: CXF-4723
>                 URL: https://issues.apache.org/jira/browse/CXF-4723
>             Project: CXF
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.7.1
>            Reporter: Aki Yoshida
>            Assignee: Aki Yoshida
>             Fix For: 2.5.8, 2.6.5, 2.7.2
>
>
> This problem depends on how namespaces are declared for global attributes and 
> when it occurs, the transformed output will contain a duplicate namespace 
> declaration.
> Concretely, the outTransform feature transforms the input:
>   <soap:Header>
>     <Action 
> xmlns="http://www.w3.org/2005/08/addressing";>http://apache.org/hello_world_soap_http/Greeter/greetMeRequest</Action>
>     <customer:CustomerKey xmlns="http://www.w3.org/2005/08/addressing"; 
> xmlns:customer="http://example.org/customer"; 
> xmlns:wsa="http://www.w3.org/2005/08/addressing"; 
> wsa:IsReferenceParameter="1">Key#123456789</customer:CustomerKey>
> into the non-wellformed output containing a duplicate namespace declaration 
> for wsa:
>   <soap:Header>
>     <Action 
> xmlns="http://www.w3.org/2005/08/addressing";>http://apache.org/hello_world_soap_http/Greeter/greetMeRequest</Action>
>    <customer:CustomerKey xmlns="http://www.w3.org/2005/08/addressing"; 
> xmlns:customer="http://example.org/customer"; 
> xmlns:wsa="http://www.w3.org/2005/08/addressing"; 
> xmlns:wsa="http://www.w3.org/2005/08/addressing";  
> wsa:IsReferenceParameter="1">Key#123456789</customer:CustomerKey>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to