[ http://issues.apache.org/jira/browse/AXIS2-571?page=all ]
David Illsley updated AXIS2-571:
--------------------------------
Attachment: header-read-reorg-patch.txt
This patch corrects the MessageID issue by separating the invalid cardinality
check from the header scanning.
The headers are now scanned, properties appropriately allocated and then the
invalid cardinality AxisFault thrown.
Fingers crossed this is appropriate and the patch format is correct etc.
> WS-Addressing - InvalidCardinality processing incorrect with multiple
> MessageID elements
> ----------------------------------------------------------------------------------------
>
> Key: AXIS2-571
> URL: http://issues.apache.org/jira/browse/AXIS2-571
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Versions: 0.95
> Reporter: David Illsley
> Priority: Minor
> Attachments: header-read-reorg-patch.txt
>
> A late change to the WS-Addressing SOAP Binding added the text:
> A message MUST NOT contain more than one wsa:To, wsa:ReplyTo, wsa:FaultTo,
> wsa:Action, or wsa:MessageID header targeted at a recipient; headers with an
> incorrect cardinality MUST NOT be used to populate the corresponding abstract
> properties.
> Currently the AddressingInHandler inthe case of an InvalidCardinality for
> MessageID will add the 'first' message id as a relates to on the fault reply,
> meaning that its being used as the abstract property [message id]
> I have a patch to fix this to follow shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
