axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Kurz (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-3795) Unqualified SOAP Action no longer works
Date Fri, 16 May 2008 02:02:55 GMT

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

Scott Kurz commented on AXIS2-3795:
-----------------------------------

It seems the client side problem was user error.  As it turned out a bug in my code was causing
me to new up my ServiceClient with the wrong QName passed into my service builder 

          // serviceQName was incorrect
           WSDL11ToAxisServiceBuilder serviceBuilder =
                new WSDL11ToAxisServiceBuilder(wsdlDefinition, serviceQName, portName);
           // .. go on to build AxisService, etc. from builder then new up client
            serviceClient = new ServiceClient(configContext, axisService);

So this explains why my client was sending 'urn:sendGuessAndName' instead of simply 'sendGuessAndName'
which is what's in the WSDL.     (Well, not fully, but it at least says it's not a bug that
the client didn't send exactly what's in the WSDL).

I'm not sure if then we consider the 2nd "problem" as a problem still or not.

That is, should the engine, on the service side, be able to match the SOAP envelope's action:
''urn:sendGuessAndName'  with the ''sendGuessAndName'  in the WSDL?

It does at least seem like something changed recently, as even with this bug in my client
code, I didn't observe this behavior... so I'll leave this JIRA open giving anyone a chance
to comment. 

Thanks

> Unqualified SOAP Action no longer works
> ---------------------------------------
>
>                 Key: AXIS2-3795
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3795
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: Addressing
>    Affects Versions: 1.4
>            Reporter: Scott Kurz
>            Priority: Minor
>         Attachments: guessAndGreet.wsdl
>
>
> I noticed that an unqualified soapAction, e.g.:
>     ....
>     <wsdl:binding name="GuessAndGreetSoapBinding" type="tns:GuessAndGreet">
>         <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
>         <wsdl:operation name="sendGuessAndName">
>             <wsdlsoap:operation soapAction="sendGuessAndName"/>
>              ....
> used to work but now does not.     (Not sure exactly of the earlier working versions
and now I'm on some 1.4 build).
> The failure happens as my ServiceClient sends this in the SOAP envelope:
>   <wsa:Action>urn:sendGuessAndName</wsa:Action>
> which the engine can't match against anything on the service side, throwing an exc:
> org.apache.axis2.addressing.AddressingFaultsHelper triggerActionNotSupportedFault triggerActionNotSupportedFault:
messageContext: [MessageContext: logID=urn:uuid:2EF546E3E9D1FEA1C31210364327358] problemAction:
urn:sendGuessAndName
> I'm guessing this is a bug rather than a conscious decision to not support this style
soapAction in Axis2, but I haven't been following  discussions so I'm not sure.
> Thanks, Scott

-- 
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message