You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2010/05/14 19:52:42 UTC

[jira] Updated: (WSCOMMONS-180) Adding soap attributes to a soap message using a different soap namespace prefix get the default soap namespace prefix

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

Andreas Veithen updated WSCOMMONS-180:
--------------------------------------

    Fix Version/s: Axiom 1.2.10
                       (was: Axiom 1.2.9)

Can you also provide a test case, please?

> Adding soap attributes to a soap message using a different soap namespace prefix get the default soap namespace prefix
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: WSCOMMONS-180
>                 URL: https://issues.apache.org/jira/browse/WSCOMMONS-180
>             Project: WS-Commons
>          Issue Type: Bug
>          Components: AXIOM
>         Environment: Axiom 1.2.2 / Axis2 1.1.1
>            Reporter: Jörg Eichhorn
>            Assignee: Andreas Veithen
>            Priority: Minor
>             Fix For: Axiom 1.2.10
>
>         Attachments: patch.diff
>
>
> When adding a new soap attribute to a soap message which does not use the default soap namespace prefix, the attribute is added with the default soap namespace prefix (which is added to the document).
> The setAttribute(String attributeName, String attrValue, String soapEnvelopeNamespaceURI) method of the classes org.apache.axiom.soap.impl.dom.SOAPHeaderBlockImpl and org.apache.axiom.soap.impl.llom.SOAPHeaderBlockImpl should check if the namespace with the given uri is already defined.

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