axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Victor (JIRA)" <>
Subject [jira] [Commented] (AXIS2-4264) Empty action not applied in CommonsHTTPTransportSender
Date Fri, 21 Aug 2015 11:39:45 GMT


Victor commented on AXIS2-4264:

And it is the same for a null soapAction with SOAP1.2, the corresponding default value is
empty soap action as Alexis highlighted in one of its comments…

> Empty action not applied in CommonsHTTPTransportSender
> ------------------------------------------------------
>                 Key: AXIS2-4264
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.3, 1.4, 1.4.1, 1.5
>            Reporter: Alexis Midon
>            Assignee: Rich Scheuerle
>             Fix For: 1.6.0
>         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]

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message