I agree, most of the time its static, I do have one method, where the
url, regularly changes. My main point was, this is not one of
witango's strengths. And my RB example, shows a complete, 3 lines of
code approach.
So I am sure you will find what works best for you, but I have been
bitten many times, starting down a solution with witango, that
involved soap or xml, that I had to completely abandon, due to
limitations, or bugs, so beware.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Aug 31, 2006, at 1:10 PM, Scott Cadillac wrote:
Hi Roland,
Technically speaking, what Robert said is true, but speaking from
experience, I find this rarely to be the case.
If the SOAP service you're calling is for a commercial vendor, then
I would find it highly unlikely that the WSDL will change very
often - and when it does, it's more like they'll be adding to the
function list rather than changing the parameter scope of an
existing function.
After eating the SOAP dog food for several years, you learn not to
make even subtle changes to published specs - because typically
many of your service consumers are not using automated tools with
WSDL, but are actually running a custom posts.
Yes, I recommend using a development tool that supports SOAP
interfacing, i.e., Visual Studio. But if the entry is too steep,
then custom posting with XML is an option.
Take it for what it's worth. Hope this helps.
Scott Cadillac,
Email: [EMAIL PROTECTED]
http://scott.cadillac.bz
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
