Re: AW: AW: HTTPAPI / call webservice in base64binary-code

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

If you look at the parameters for each API (listed in HTTPAPI_H) you'll 
see that both http_url_post_xml() and http_url_post_stmf() provide a 
SOAPAction parameter.  If the web service requires a SOAP action, then 
you'll need to pass this parameter, no matter which routine you use.

However, the error message you posted sounds like your data is invalid. 
  Maybe you still have a CCSID problem?  Make sure that your stream file 
is already translated to ASCII or Unicode or whatever you need to send. 
  (This can be done automatically by the open() API, if the correct 
syntax is used.)   http_url_post_stmf() does not translate the data to 
ASCII for you, but http_url_post() and http_url_post_xml() do translate 
it for you -- so that's another possibility.


Marcus Schmidtke (Besitec IT DEBRE) wrote:
> Hey Scott,
> 
> Of course you are right. It's stupid way to convert character for
> character from ebcdic to ascii. I have thrown the QDCXLATE away. Now the
> encode- and decode-procedures are running absolut fantastic. Many thanks
> for it :)) 
> 
> Now only one problem is occured: 
> If I put the complete file in a variable and make a request with the
> http_url_post_xml()-API everything is okay.
> But if I use the http_url_post_stmf()-API i get the error "Server was
> unable to process request. ---> Data at the root level is invalid.
> Line 1, position 1".
> 
> I wonder that in first API i could enter SOAP-post and
> SOAP-action-parameter, in second one only the post-parameter. Could this
> be the problem?
> 
> Maybe it's a stupid question but as written I'm not used in working with
> web-services.
> 
> Thanks a lot and best regards
> Marcus

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------