Why add a wrapper to the MS WSDL tool? So that you can verify that your web services, be they written with Axis or anyone else's SOAP toolkit, work with .NET clients.
This task is dependency aware when using a file as a source and destination; so if you <get> the file (with usetimestamp="true") then you only rebuild stuff when the WSDL file is changed. Of course, if the server generates a new timestamp every time you ask for the WSDL, this is not enough...use the <filesmatch> <condition> to to byte for byte comparison against a cached WSDL file then make the target conditional on that test failing.
Attribute | Description | Example |
destFile | name of file to generate. Required | ApacheNet.cs |
srcFile | name of WSDL file to use. Required if url is not set | service.wsdl |
url | url to retrive WSDL from. required if srcFile is unset | http://localhost/service?wsdl |
server | generate server stubs, not client proxy code. optional; default false | "false"(default) |
namespace | namespace to place the source in. optional; default "" | Apache.Net |
language | language; one of "CS", "JS", or "VB" optional; | "CS" (default) |
failOnError | Should failure halt the build? | "true"(default) |
extraOptions | Any extra options which aren't explicitly supported by the task, like all the proxy server config stuff |