The idea to have a WSDL or a WADL is interesting. It helps in integrations between system-system (without human coding/support), and allows more sophisticated software to consume APIs. Instead of creating something to generate the API externally, why not add a plugin into CloudStack that generate the web service description? Then, systems that have the ability to read the WSLD could do that on the fly.
Common Webservices already do this type of function. For WSDL, frameworks normally respond with a WSDL when you post a request such as “ http://webservice.example/endpoint?WSDL” The same can be done for WADL, normal RET web services return a WADL when you request for a URL such as http://localhost:8080/applicationname/application.wadl WADL and WSDL are formal ways of describing web service methods, their parameters, outputs, and a description of the method. On Wed, Nov 23, 2016 at 8:03 AM, Rohit Yadav <rohit.ya...@shapeblue.com> wrote: > Mauricio, > > > As far as I'm aware, we don't have any tooling to support this but you're > right such a tool would consume response from listApis call. > > You may want to write such a tool for your use-case and maybe publish it > on github/pypi/etc. > > > Regards. > > ________________________________ > From: Mauricio Schaepers <m.schaep...@vsqloud.de> > Sent: 21 November 2016 20:23:29 > To: dev@cloudstack.apache.org > Subject: WSDL for CloudStack > > Hi all, > > I'm trying to automate several things including CloudStack. The Automation > Framework I'm using requests a WSDL File. > > Does anybody has already created a WSDL File for the REST API? > > Or on other hand, if I setup the WSDL document, is anybody interested? > I mean, in the end it should be "just" converting the ListAPIs command to > a valid WSDL syntax > > Mauricio > > rohit.ya...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > -- Rafael Weingärtner
