[
https://issues.apache.org/jira/browse/AXIS2-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexis Midon updated AXIS2-4264:
--------------------------------
Attachment: AXIS2-4264.patch.txt
I attached a patch implementing the logic described above.
This patch could be applied to 1.3, 1.4.1 or 1.5.
> Empty action not applied
> ------------------------
>
> Key: AXIS2-4264
> URL: https://issues.apache.org/jira/browse/AXIS2-4264
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: transports
> Affects Versions: 1.5, 1.4.1, 1.4, 1.3
> Reporter: Alexis Midon
> Attachments: AXIS2-4264.patch.txt
>
>
> Hello there,
> I'm invoking a service using a ServiceClient, the wsdl operation declares an
> empty soapAction.
> However the soapActiuon actually sent is "urn:anonOutInOp" which the server
> refuses. This action is the action the anonymous operation "urn:anonOutInOp"
> and is set by the ServiceClient.
> Later when CommonsHTTPTransportSender#findSOAPAction [1] is invoked, if the
> action of the MessageContext is null or empty, the operation action is used.
> The empty case seems like a bug, because this is the action set in the wsdl
> and it is not applied.
> This opinion is strengthened by the fact that other senders do not have this
> behavior.
> The right behavior would be:
> if null ; use the operation action as a default
> if empty ; send an empty soapAction
> Could you confirm please?
> Alexis
> [1] http://is.gd/m0Mt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
