| Re: [kapua-dev] REST API vs Web UI |
It should be on the REST API servlet root (although it’s not an actual file, but it’s served dynamically by the servlet itself). So I’d remove the /api from the JSON URI and click Explore to make Swagger UI load it again.
--
Claudio Mezzasalma | Eurotech
Da: <kapua-dev-bounces@xxxxxxxxxxx> per conto di Henryk Konsek <hekonsek@xxxxxxxxx>
Risposta: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Data: lunedì 20 marzo 2017 12:34
A: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Oggetto: Re: [kapua-dev] REST API vs Web UI
Hi Claudio,
I can open Swagger UI, many thanks! But apparently Swagger can't locate swagger.json file (see screenshot). Any idea where swagger.json can be?
Thanks!
pon., 20 mar 2017 o 10:35 użytkownik Mezzasalma, Claudio <Claudio.Mezzasalma@xxxxxxxxxxxx> napisał:
Well, in my Vagrant based setup the REST API servlet is at http://localhost:8080/api (with the REST resources starting at http://localhost:8080/api/v1) so browsing to http://localhost:8080/api/doc brings up Swagger UI. Isn’t that the case for the Docker/OpenShift deployment?
However, looking at your URIs, maybe http://172.30.174.96:8080/doc could be the winner?
--
Claudio Mezzasalma | Eurotech
Da: <kapua-dev-bounces@xxxxxxxxxxx> per conto di Henryk Konsek <hekonsek@xxxxxxxxx>
Risposta: kapua developer discussions <kapua-dev@xxxxxxxxxxx>Data: lunedì 20 marzo 2017 10:08
A: kapua developer discussions <kapua-dev@xxxxxxxxxxx>Oggetto: Re: [kapua-dev] REST API vs Web UI
Thank you Claudio.
I'm not sure what kapua_server_address in http://<kapua_server_address>/api/doc is :) Do you mean API server process address? So Swagger API is exposed on http://api-server:8080/api/doc ?
I can see Jersey page on http://172.30.174.96:8080/, but http://172.30.174.96:8080/api/doc and http://172.30.174.96:8080/api returns 404.
What is the proper URL to get access to REST API docs then?
sob., 18 mar 2017 o 17:54 użytkownik Mezzasalma, Claudio <Claudio.Mezzasalma@xxxxxxxxxxxx> napisał:
Yes, it’s totally correct. The GWT console uses its own RPC calls and not our REST APIs; the Patternfly console, in the other hand, uses only REST calls, but unfortunately it only covers a few calls about Devices and Users currently. However, by opening http://<kapua_server_address>/api/doc you can see the updated Swagger documentation for all the methods currently available (maybe some of the new datastore REST APIs are missing, I can’t recall whether they have been already merged or not).
Hope this helps!
--
Claudio Mezzasalma | Eurotech
Da: <kapua-dev-bounces@xxxxxxxxxxx> per conto di Henryk Konsek <hekonsek@xxxxxxxxx>
Risposta: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Data: venerdì 17 marzo 2017 18:33
A: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Oggetto: [kapua-dev] REST API vs Web UI
Hi,
I wanted to play a bit with our REST API and document it. To be exact I'd like to list events associated with a given device. I attempted to reverse engineer communication used by web UI to see what REST calls it performs. But I see that apparently our UI uses some GWT-specific calls, not our REST API - is that correct? (see attachments)
Cheers!
Errore. Il nome file non è specificato.--
Henryk Konsek
_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev--
Henryk Konsek
_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev_______________________________________________--
Henryk Konsek
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev
