[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Missing tags in the web service XML creation

Scott - Upon reading the articles I am leaning towards your idea.

- If it is worth a question can you please tell me how different is
EXPAT compared to IBM supplied XML-SAX parser? I just started reading
documentation on IBM for XML parsing.

- I am trying to understand your sample programs in LIBHTTP and find
which is going to be the version I should use as there seems to be
different methods of XML parsing in there.

- Also I do not know if I can use SOAPUI since our company has already
developed a generic RPG application to generate a XML file to POST to
the web service. Would that cause any issues in using your EXPAT utility
to parse the response file?

- Lastly, your example in HTTPXMLR4 seems to contain both HTTP POST as
well as EXPAT parsing. Is that correct?

Thanks advance,


Message: 1
Date: Thu, 27 Aug 2009 12:46:34 -0500
From: Scott Klement <sk@xxxxxxxxxxxxxxxx>
Subject: Re: Missing tags in the web service XML creation
To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Message-ID: <4A96C67A.4010103@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed


> Here is what is happening. The tags between <q0:paymentRequest> and
> </q0:paymentRequest> are not being generated.

I just want to point out that you can use HTTPAPI with SoapUI. To get 
this service working.  It's a little more effort than using WSDL2RPG, 
but if you have a looming deadline, this might get you going quicker 
than waiting for Thomas to update WSDL2RPG.

Surely doing that is 100 times simpler than switching to another 
technology like MQ!

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or
entity to which it is addressed. If the reader of this e-mail is
not the intended recipient or his or her authorized agent, the
reader is hereby notified that any dissemination, distribution or
copying of this e-mail is prohibited. If you have received this
e-mail in error, please notify the sender by replying to this
message and delete this e-mail immediately.
This is the FTPAPI mailing list.  To unsubscribe, please go to: