axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Victor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AXIS2-4264) Empty action not applied in CommonsHTTPTransportSender
Date Mon, 24 Aug 2015 07:31:46 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708899#comment-14708899
] 

Victor commented on AXIS2-4264:
-------------------------------

I could, but first I would prefer to get feedback about what should be expected, because
I'm not an expert in SOAP and I'm not clear when it is then needed to use AxisOperation for
the SoapAction… Actually I'm not even clear if the WSDL's SoapAction is available from code
through the AxisOperation or through the MessageContext (i.e. the Option object)… I'm currently
taking over on big base of code using Axis, so I'm not even sure if it was coded correctly
with respect to how Axis is meant to be used, but I can put a bit of my time to help fixing
this issue.

In terms of requirements:
To me, if there is no soapAction defined in the WSDL or if there is an empty value is the
same thing: a empty soap action should be sent.
For SOAP 1.2, it is the specs that says so.
For SOAP 1.1, no soap action is considered invalid WSDL: I would say it's better to follow
SOAP 1.2 spec on that, but maybe that's where you thought we should use the AxisOperation
as the soap action?

So to fixes this, I'm not sure where it should really happen… but if it has to be in CommonsHTTPTransportSender
and these requirements I wrote are correct, I can give it a shot.

> Empty action not applied in CommonsHTTPTransportSender
> ------------------------------------------------------
>
>                 Key: AXIS2-4264
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4264
>             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] http://is.gd/m0Mt



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message