|
True, Alex's template should do what you need, with minor modifications. My concern about it is that the envelope is hardcoded in the compile time array. With the CGIDEV2 template process the envelope can be modified without needing to recompile the program. You could even build a generic service program that used different template sections depending on what web service you were trying to access. I am not very familiar with soap, so I don't know what areas of the envelope would need to be changed to access different web services. But I always try to avoid hard coding things if I can, it always comes back and bites you. Joe Lee >>> joepluta@xxxxxxxxxxxxxxxxx 03/23/2004 12:49:45 >>> > From: Joe Lee > > You might also look at using the CGIDEV2 templates for creating the soap > envelope. With Alex's template, I think I'm going to be able to do this without too much trouble. The beauty of the approach is that I use the free TCP/IP sniffer ethereal that David mentioned to trace the communication from the WDSC generated client, and then I simply plug the pieces into Alex's example. I suspect this will be a relatively easy operation, and once it's done I may even be able to make it available to the outside world. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.