I appreciate the response, but a SOAP service without a WSDL definition severely lowers usability. I'm a Java programmer, and with a WSDL I can generate a Java API for ISPConfig. I read another forum post where a .NET programmer wanted to do the same thing. Sure, I could spend hours mapping it all out myself but to have every developer who wants to work with ISPConfig do that is extremely inefficient and it makes the most sense to have the creator of the SOAP service make this file.
I know, it's open source... take it as it is or get involved. It's a good product but this glaring omission is holding it back I feel. I'm happy to develop and contribute a WSDL file for the project, but before I spend the time doing that I want to make sure there isn't one currently in development or that there are no current plans to fix the ?wsdl auto-generation. Any ideas on that?