I believe the HTTP API will use the same underlying message format (proto def)
and hence the request/response value objects (java) needs to be auto-generated
from the proto files for it to be used in Jersey based java rest client?
On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewski
<jani...@gmail.com> wrote:
I suspect jar is deprecated and includes only old API used by mesoslib. The
goal is to create HTTP API and stop supporting native libs (jars, so, etc).
I think you shouldn't use that jar in your project.
wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
vijikar...@yahoo.com> napisał:
> Hello,
>
> I am writing a rest client for "operator APIs" and found that some of the
> protobuf java classes (like "include/mesos/v1/quota/quota.proto",
> "include/mesos/v1/master/master.proto") are not included in the mesos jar
> file. While investigating, I have found that the "Make" file does not
> include these proto definition files.
>
> I have updated the Make file and added the protos that I am interested in
> and built a new jar file. Is there any reason why these proto definitions
> are not included in the original build apart from the reason that the APIs
> are still evolving?
>
> Regards
> Vijay
>
