Re: Web Services (again!)

[Scott Klement <web400@xxxxxxxxxxxxxxxx>]

Aaron,

Although SoapAction is not manditory, virtually every SOAP web service 
that I've seen uses it.  And I've used all of those web services with 
SoapUI, and it has always passed the SoapAction for me.  Furthermore, I 
use that SoapAction value (the one sent by SoapUI) when putting together 
the HTTPAPI code to call the web service from RPG.  So I know it's there.

However, SoapAction is not manditory.  So maybe SoapUI didn't show you a 
SoapAction in your case because the web service you were calling didn't 
require a SoapAction?

Also, in SOAP 1.2, instead of using a SoapAction HTTP header, they added 
SoapAction to the content-type.   So the content-type looks like this:

Content-Type: application/soap+xml; action="your-soapaction-here"

So it's still there, but you might have missed it because it's sent a 
little differently.

Not sure what any of this has to do with Jon's question though... he 
wasn't having a problem wtih the SoapAction, he was having a problem 
with userid/password.


On 4/9/2010 8:39 AM, Aaron Bartell wrote:
> Also, make sure that you are sending the SOAPAction value in the HTTP
> request headers as SOAPUI doesn't include those by default (in my
> experience).