Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@axis.apache.org
Date: Mon, 14 Oct 2013 13:49:42 +0000 (UTC)
From: "Andreas Veithen (JIRA)" <jira@apache.org>
To: java-dev@axis.apache.org
Message-ID: <JIRA.12661074.1375346074832.59941.1381758582501@arcas>
In-Reply-To: <JIRA.12661074.1375346074832@arcas>
References: <JIRA.12661074.1375346074832@arcas>
Subject: [jira] [Comment Edited] (AXIS2-5597) The adressing module adds the
 addressing namespace declaration in the header element, which is not
 allowed by BP 1.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andreas Veithen edited comment on AXIS2-5597 at 10/14/13 1:48 PM:
------------------------------------------------------------------

Yes, the schemaValid attribute is indeed set by the monitor. It's interesting to see how this is done in the monitor tool that is distributed by WS-I:

{code}
    if soapMessage != None:
        messageContents.append(soapMessage)
        messageContents.set('validXml', 'true')
        # TODO - Actually validate the messages
        messageContents.set('schemaValid', 'true')
    else:
        messageContents.set('validXml', 'false')
        messageContents.set('schemaValid', 'false')
{code}


was (Author: veithen):
Yes, the schemaValid attribute is indeed set by the monitor. It's interesting to see how this is done in the monitor tool that is distributed by WS-I:

    if soapMessage != None:
        messageContents.append(soapMessage)
        messageContents.set('validXml', 'true')
        # TODO - Actually validate the messages
        messageContents.set('schemaValid', 'true')
    else:
        messageContents.set('validXml', 'false')
        messageContents.set('schemaValid', 'false')

> The adressing module adds the addressing namespace declaration in the header element, which is not allowed by BP 1.2
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-5597
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5597
>             Project: Axis2
>          Issue Type: Bug
>          Components: Addressing
>    Affects Versions: 1.6.2
>            Reporter: Maarten van den Broek
>
> Validation of an axis2 message with an addressing header gives a BP1600 error.
> This issue can probably be resolved by changing line 210
>    addressingNamespaceObject = header.declareNamespace(addressingNamespace, WSA_DEFAULT_PREFIX);
> in the class org.apache.axis2.handlers.addressing.AddressingOutHandler to
>     addressingNamespaceObject = envelope.declareNamespace(addressingNamespace, WSA_DEFAULT_PREFIX);
> Maybe more changes are necessary.


--
This message was sent by Atlassian JIRA
(v6.1#6144)

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