Having a SDK to ease the writing of the client code is a good idea.
Client code is about building 3rd party apps on top of Kapua so we should also support
multiple bindings to guarantee the highest level of access to the platform. More over, in my experience, not only it requires coding effort but it also needs to
be constantly kept aligned with the API. So i think that the code generation approach is the best,
- reduces the coding effort
- automatically keeps the SDK aligned with the API
- supports multiple bindings
Swagger supports code generation but it is not the only tool, one may want to use
wadl2java (also used in SOAPUI I guess), maybe there are plugins for IDEs. These will produce full-object wrappers.
When developing client code the most boring part of the job is to deal with model objects.
We could support a lightweight client library that uses apache http-components
(which is rest framework agnostic) or jersey classes to manage http connections; swagger can then generate the code for model objects in the bindings that we want to support (which initially
will be java).
So I wouldn't develop an on-purpose library here.
Stefano Morson