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

Jarek Gawor resolved AXIS-824.
------------------------------

    Resolution: Won't Fix
    
> SOAPAction Header not mapped to operation
> -----------------------------------------
>
>                 Key: AXIS-824
>                 URL: https://issues.apache.org/jira/browse/AXIS-824
>             Project: Axis
>          Issue Type: Bug
>          Components: Basic Architecture
>    Affects Versions: 1.1rc2
>         Environment: Operating System: Other
> Platform: Other
>            Reporter: Kevin Jones
>            Assignee: Jarek Gawor
>         Attachments: actionhandler2.patch, actionhandler.patch
>
>
> I have a WSDL doc that adds a SOAPAction value (i.e. doesn't leave it blank). 
> If
> I run my client against
> http://localhost/orinoco/services/Orinoco then it works
> If I run it against
> http://localhost/orinoco/services/
> then I get the following
>    <faultstring>The AXIS engine could not find a target service to invoke! 
> targetService is urn:com.develop.ejws:orinoco#get
> BookAvailabilityByISBN</faultstring>
> My wsdd is generated from the WSDL and I've also added the following entries
>     <handler name="ActionHandler"
> type="java:org.apache.axis.handlers.http.HTTPActionHandler"/>
>     <transport name="http">
>         <requestFlow>
>             <handler type="ActionHandler"/>
>             <handler type="URLMapper"/>
>             <handler 
> type="java:org.apache.axis.handlers.http.HTTPAuthHandler"/>
>         </requestFlow>
>     </transport>
> I've tried with both an RC2 generated client and a command line utility that I
> have. both set the SOAPAction header (I can see the trace in tcpmon) but I
> always get the same fault.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to