> From: Narayanan R Pillai
> 
> The equivalent for this case as an HTTP request is :
> 
>
http://servername:8080/sanjose/service/Repair?method=getRepairHeader&in1
=B
> TO&in0=123456

Your request looks like a standard HTTP request.  From your post, I get
the idea that the response is wrapped in a SOAP document and you have to
parse out the value.

It's evidently not quite that simple with WebSphere.  When I try your
technique to access my web server, I get the phrase:

        And now... Some Services

With WebSphere, it looks like the request has to be wrapped in SOAP as
well.  This means that I have to send an entire SOAP document (some 700
bytes of overhead) and then get back another SOAP document and parse out
the response.

It may depend on how you generate your web service.  I used type
"RPC/Literal", which I had assumed would remove most of the wrapping,
but I'm not sure.

Joe



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.