Hi Scott-

Did you supply the WSDL?

----- Original Message ----- From: "Scott Kurz (JIRA)" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Saturday, May 10, 2008 9:53 AM
Subject: [jira] Updated: (AXIS2-3795) Unqualified SOAP Action no longer works



[ https://issues.apache.org/jira/browse/AXIS2-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Kurz updated AXIS2-3795:
------------------------------

   Description:
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






 was:
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:getGreetings</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:getGreetings


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







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
   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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to