× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



hi Robert,

Yes, I think you're right, Robert. For example, if your XML currently looks like this:

<myXML>Data</myXML>

then in a wrapped SOAP message it'd look something like this:

<soap:Envelope xmlns:soap="http://www.w3.org/2001/12/soap-envelope";
xmlns:tns="urn:WellingtonRoyceXmlWrapper">
<soap:Body>
<tns:YourRequest>
<tns:Data>&lt;myXML&gt;Data&lt;/myXML&gt;</tns:Data>
</tns:YourRequest>
</soap:Body>
</soap:Envelope>

Granted, I made up some of the names ("YourRequest", "Data", the TNS namespace) but that's the general idea. The original XML is escaped into character entities and placed in a parameter of a SOAP message.

It shouldn't be hard to build this message in an RPG program, and send it via HTTPAPI. The hardest part will be escaping the existing XML data -- but it shouldn't be too bad. If you can't figure it out, let me know.

When the output message is sent back, you can use HTTPAPI's XML parser to extract the original XML data -- it'll automatically "unescape" it for you.

-SK


On 12/20/2012 11:53 AM, Robert J. Mullis wrote:
Thanks Scott.

My XML will stay the same. It is "wrapped" in a SOAP message for the web
service. If I understand everything correctly, I should still be able to
use my same HTTP process that I am using now. The only difference is that I
will need to "wrap" the XML in a SOAP message, before sending it. When the
XML is returned, I will need to remove the SOAP message "wrapper", before I
can parse the XML. Is my assumption correct?


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-2024 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.