[
https://issues.apache.org/jira/browse/AXIS2-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626088#action_12626088
]
Brian DePradine commented on AXIS2-3987:
----------------------------------------
The WS-Addressing spec does say that the wsa:MessageID header is optional, but
that isn't the whole story. If the operation that you are trying to invoke is
actually a two-way mep, e.g request-response, then the wsa:MessageID header is
actually required, according to the same spec. Axis2 will enforce this for
services deployed to it, and reject the message if it does not contain a valid
message id. It is true that Axis2 clients will also send a wsa:MessageID header
for a one-way mep, even though it is not required, but this hasn't been an
issue until now.
At the moment there is no way to disable the setting of the wsa:MessageID
header because the clients always generate a message id, if one isn't
explicitly specified.
> Axis2 Addressing treats MessageID as a required element
> -------------------------------------------------------
>
> Key: AXIS2-3987
> URL: https://issues.apache.org/jira/browse/AXIS2-3987
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: Addressing
> Environment: Ubuntu, jdk 1.5
> Reporter: Isuru Eranga Suriarachchi
>
> According to both WS-Addressing final and submission specifications, the
> Message Id is an optional element in the header. But when I engaged Axis2
> addressing to a simple client and set only the Action, it adds a message Id
> as well. I tried the following option as well. But it didn't work.
> options.setProperty(INCLUDE_OPTIONAL_HEADERS, Boolean.FALSE);
> So I can't create a message without the optional element "MessageID" using
> Axis2..
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
