No, as far as I know, alpaca is the first of its type. As the author of the code, I can guarantee good quality of the generated client code. I have written the templates such that they follow their respective language conventions and ecosystems.
I have been using this since the beginning for my open source project https://github.com/pksunkara/alpaca. They provide very good support. And the features are awesome.
Being a WSDL is not the aim here. Generating client libraries in multiple programming languages is.
But, to do that I need a format using which people can define their API. I used JSON and only supported the elements that I needed to generate the client libraries.
I tried searching for a program which generates client libraries in different programming languages and failed.
Could you please link if something does it? From what I gather, the above mentioned sites only provide methods of describing the API and/or Automating the API on the server side. Nothing is said about client libraries.
EDIT: OAUTH Consumption is not the main priority here. The problem I intended to solve is automating the development and maintaing of API client libraries in several different languages.
That said, I intend to add support for OAUTH consumption too.
Something like this what I think github needs. Github should complement developers working using the cli. (git-send-email, git-format-patch, git-am). I hope they concentrate on this soon.
Good Strategy, Bad Strategy https://www.goodreads.com/book/show/11721966-good-strategy-b...