Thanks for the reply. Happy to discuss, although we’ve decided to go with a templating based solution off an EMF model.
Just to preface, a few of our key requirements, which are pretty common for any large engineering org.
a. code gen has to be runnable as part of our build process
-> if that’s via a set of jars, we don’t particularly mind, but it has to be from model to src as part of our processes. standard stuff for repeatable builds. We are happy to do this off an EMF/XMI model, whatever.
b. we have to be in full control of the code gen
-> if we need to make changes, we need to make changes quickly
c. ideally open source
-> the idea of not being able to fix bugs, or relying on an external company to fix bugs or add features doesn’t work for us
We are happy to pay for the modeling tool, but want much more freedom around code gen.
So, with that in mind, the swagger generator we are working towards is as follows. This is very specific to our use cases.
- resources are specified as a single entity, and you can specify on this single entity which verbs are supported
- the resource itself and its attributes are the main representation
- you can have an association to other representations
- GET params etc live on the main resource entity
This way, we can encode all of our standards for URL naming etc in the generator, rather than leaving it up to each engineer to specify on each of the verb entities. The current VP swagger generator is flexible, but too flexible for us - it’s quite easy to accidentally get one path for a GET and another for the PUT.