Re: receive Dynamic XML

[Donnie Barrow <ddbarrow@xxxxxxxxx>]

   with that example there is only one variable being passed back.
   rc = http_url_post_xml(
   'http://www.webservicex.net/CurrencyConvertor.asmx'
   : %addr(SOAP) + 2
   : %len(SOAP)
   : *NULL
   : %paddr(Incoming)
   : %addr(rate)

   please give me a suggestion on how to handle a data structure where I
   am using an external file definition. Would I incorporate the routine
   in ex17?
     __________________________________________________________________

   From: Mike Krebs <mkrebs@xxxxxxxxxxxxxxxxxx>
   To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
   Sent: Thursday, November 6, 2014 2:28 PM
   Subject: RE: receive Dynamic XML
   Sounds like you are on the right track.
   If you have problems writing INCOMING, share some XML and there are a
   bunch of us that can help out. But with multiple data elements, you
   will have to use some global variables or data structures to keep track
   of the results.
   -----Original Message-----
   From: [1]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   [mailto:[2]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Donnie
   Barrow
   Sent: Thursday, November 6, 2014 11:57 AM
   To: HTTPAPI and FTPAPI Projects
   Subject: Re: receive Dynamic XML
   Thank you for you response Here is what I am doing. I getting item
   info/availability from a webservice. since it will involve multiple
   warehouses the xml will return lists aka arrays of warehouse item
   availability.[UGHHH]  So I took a bit of EXAMPLE16 & EXAMPLE17 and used
   it since it was parsing the return data. In my case it will be a huge
   chunk of data to parse especially with the arrays....SO I didn't want
   to write it to the IFS [like in EXAMPLE17] but rather parse send the
   data back into the program parms.
         From: Mike Krebs <[3]mkrebs@xxxxxxxxxxxxxxxxxx>
   To: HTTPAPI and FTPAPI Projects <[4]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
   Sent: Thursday, November 6, 2014 12:15 PM
   Subject: RE: receive Dynamic XML

   I think http_url_post_xml allows you to work with the returned data
   directly. EXAMPLE16 is showing this by calling INCOMING for each
   element in the returned xml.
   -----Original Message-----
   From: [5]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   [mailto:[6]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Scott
   Mildenberger
   Sent: Thursday, November 6, 2014 10:29 AM
   To: HTTPAPI and FTPAPI Projects
   Subject: RE: receive Dynamic XML
   I have used both the _raw and _xml procedures for either
   http_url_get/post depending on what you are using, they allow you to
   specify a procedure that gets called when data is received.  They are
   used in some of the provided examples if you search for them.
   Scott
   -----Original Message-----
   From: [7]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   [mailto:[8]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Donnie
   Barrow
   Sent: Wednesday, November 05, 2014 4:59 PM
   To: HTTPAPI and FTPAPI Projects
   Subject: receive Dynamic XML
    i need some guidanceMy rpgle free program is calling a webservice. I
   used Scott Klement's example17 but I do not want to write the response
   soap to the IFS. Is there anyway to receiveand parse the response xml
   in the program without writing to the IFS Donovan BarrowDBarrow
   Consulting
   -----------------------------------------------------------------------
   This is the FTPAPI mailing list.  To unsubscribe, please go to:
   [9]http://www.scottklement.com/mailman/listinfo/ftpapi
   -----------------------------------------------------------------------
   -----------------------------------------------------------------------
   This is the FTPAPI mailing list.  To unsubscribe, please go to:
   [10]http://www.scottklement.com/mailman/listinfo/ftpapi
   -----------------------------------------------------------------------

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

References

   1. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   2. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   3. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
   4. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
   5. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   6. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   7. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   8. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   9. http://www.scottklement.com/mailman/listinfo/ftpapi
  10. http://www.scottklement.com/mailman/listinfo/ftpapi
  11. http://www.scottklement.com/mailman/listinfo/ftpapi

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