axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cory Wilkerson" <>
Subject RE: How does Axis handle soapAction?
Date Fri, 01 Aug 2003 21:43:02 GMT
Sorry about that Wendy -- got carried away in my response.

-----Original Message-----
From: Anne Thomas Manes []
Sent: Friday, August 01, 2003 2:18 PM
Subject: Re: How does Axis handle soapAction?

The attribute is "SOAPAction", not "header".
The value specified in the attribute must be specified in the SOAPAction: HTTP header on the
SOAP request message. It gives the SOAP server a hint on how to process the message. 

----- Original Message ----- 
From: Cory Wilkerson <>  
Sent: Friday, August 01, 2003 3:07 PM
Subject: RE: How does Axis handle soapAction?

The attribute "header" of element "operation" in the soap namespace
A) Appears as an HTTP header
B) I believe it's sole purpose is to assist the consuming framework in routing the incoming
request to the appropriate "service".

-----Original Message-----
From: Wendy Smoak []
Sent: Friday, August 01, 2003 1:23 PM
To: ''
Subject: How does Axis handle soapAction?

I picked this up from the example that Richard Hansen posted on 7/30: 

<soap:operation soapAction="RatingPortType#getRate" style="document"/> 

However, the string "RatingPortType" does not appear anywhere else in the WSDL document. 
And the examples in the document always have a URL in the soapAction

I recognize the string after the # sign as the method to be called, but what does "RatingPortType"
mean in this case? 

Should it possible match the portType name from this section? 
 <portType name="RatingServicePort"> 
        <operation name="getRate"> 
            <input message="tns:RatingRequest"/> 
            <output message="tns:RatingResponse"/> 

Thanks for your help, 

Wendy Smoak 
Applications Systems Analyst, Sr. 
Arizona State University, PA, IRM 

View raw message