[
https://issues.apache.org/jira/browse/AXIS2-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794107#comment-13794107
]
Maarten van den Broek commented on AXIS2-5597:
----------------------------------------------
The attribute @schemaValid referred to in the test assertion is an attribute on
the element in the testlog.xml that surrounds the actual message and not an
intrinsic part of the tested message. This attribute is set by the Monitoring
part of the compliancy test to true of false.
It is very well possible that it is set to false, when the Header element
contains a namespace declaration. It is quite difficult to simulate this
behaviour without setting up the whole WS-I BP testsuite. For the time being I
assume that it has been set up correctly in the test facility of the Dutch
government and it is a problem within Axis2.
In all examples of the test facility there is nowhere declared a namespace on a
header element.
> 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: [email protected]
For additional commands, e-mail: [email protected]
