[ http://issues.apache.org/jira/browse/AXIS2-891?page=all ]
Brian DePradine updated AXIS2-891:
----------------------------------
Attachment: patch.txt
This patch does the following:
1) Adds methods setUseSoapAction() and isUseSoapAction() to the Options class.
The default of isUseSoapAction() is true which preserves the current behavior.
2) Modifies the transports to check the value of isUseSoapAction()
3) Modifies the WS-Addressing handler to check that any action set on the
message context matches the action passed in the WS-Addressing action header,
otherwise a fault is thrown.
4) Updates some unit tests.
I have also tested that this works correctly using the
EchoNonBlockingDualClient sample.
> Allow the WS-Addressing action to be set, in the client, without also setting
> the SOAP action
> ---------------------------------------------------------------------------------------------
>
> Key: AXIS2-891
> URL: http://issues.apache.org/jira/browse/AXIS2-891
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Reporter: Brian DePradine
> Attachments: patch.txt
>
>
> Modify the Options class to allow a user to set the WS-Addressing action
> without also setting the soap action. This is important as, according to the
> WS-Addressing 1.0 SOAP Binding Spec, it will allow the ability to obscure the
> action through SOAP-level security mechanisms, without having to resort to
> transport level security mechanisms. Patch to follow.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
