You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ji...@apache.org on 2004/03/22 16:48:57 UTC
[jira] Commented: (AXIS-824) SOAPAction Header not mapped to operation
The following comment has been added to this issue:
Author: Davanum Srinivas
Created: Mon, 22 Mar 2004 7:48 AM
Body:
Can you please try latest CVS and let us know if you still have a problem.
thanks,
dims
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=AXIS-824&page=comments#action_26458
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=AXIS-824
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-824
Summary: SOAPAction Header not mapped to operation
Type: Bug
Status: Open
Project: Axis
Components:
Basic Architecture
Versions:
1.1rc2
Assignee: Axis Developers Mailing List
Reporter: Kevin Jones
Created: Thu, 17 Apr 2003 10:16 AM
Updated: Mon, 22 Mar 2004 7:48 AM
Environment: Operating System: Other
Platform: Other
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira