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



That is what he was talking about Booth.

Most think of IWS as the Server part. WSDL2RPG is the client side.

And I repeat my earlier comment - while I quite like what they have done with the server side (IWS) the WSDLT2RPG in my opinion is far too complicated and produces a result that just doesn't feel like RPG.


On Jul 20, 2020, at 11:27 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

IWS does a nice job and it uses RPG.

On 7/20/2020 4:05 PM, Greg Wilburn wrote:
When consuming SOAP web services, at what point is it advantageous to use WSDL2RPG versus creating the requests and handling the responses with HTTPAPI?

I ask because the WSDL is fairly complex and contains a lot of things I likely will never use. I may make 4-5 different calls for in-house use.

I've not used WSDL2RPG other than with the training examples.

Just looking for opinions.
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com


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.