Rusty, Yes, there is a start of a client, which downloads, and parses a WSDL file.
But there are so many poorly defined services, and so many options which you could use in a web service, that it hasn't been a priority to create a generic client. Instead I'm leaning toward redefining an external service using the TWiST API, and with tiny changes (like the URL of the original service), use a TWiST server as a proxy for the external service. In fact, this type of client already exists in TWiST which allows for testing the service via a web interface. ( See the example operations at http://junom.com/ws/mywebservice/ ) The testing interface is just a web page with a simple form. When the form is submitted, the values are translated into a client request, which is POSTed back to the same server (a seperate request). The only change needed for a proxy would be the external URL used for POSTing the request. Slowly this is coming together in the <ws>client API (which will be similar to <ws>return ). tom jackson On Tuesday 06 May 2008 07:50, Rusty Brooks wrote: > I don't need it as a server, I need it as a client. You mentioned > something a bout being able to use the API to make a client? -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
