[GeoNetwork-devel] Draft proposal for a GN API

Hi all, with Paul, we tried to make a proposal for making a better API for GN. The main idea is when moving services from Jeeves to Spring MVC, we also document services and agree on a common structure for the API.

Here is a first draft for comment.
https://docs.google.com/document/d/1pj6D-hTPFtBDo3drcBF0tUqOVGnzu68VaAgHaMjWTZM/edit?usp=sharing

Looking forward your feedback.

Francois

Hi Francois-Xavier,

···

Hi all, with Paul, we tried to make a proposal for making a better API for GN. The main idea is when moving services from Jeeves to Spring MVC, we also document services and agree on a common structure for the API.

It looks good ! I put some comments / random thoughs inlined in the document ; the autogenerated api doc looks also nice, and will probably makes the development easier on the project (currently grepping the entry points / opening several files before being actually able to find the corresponding java class for a controller).

Regards,

– Pierre

Dear All, during coming Bolsena codesprint, we would like to make significant progress on this topic. The target will be:

  • move services to Spring MVC following the API guideline

  • use the API in the Angular app

  • remove old services

  • add the guideline to the dev documentation

  • CFV for the API guideline

Let us know, if you’ve any comments on this.

Cheers.

Francois

···

2016-03-09 11:31 GMT+01:00 Pierre Mauduit <pierre.mauduit@anonymised.com>:

Hi Francois-Xavier,


Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140


GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Hi all, with Paul, we tried to make a proposal for making a better API for GN. The main idea is when moving services from Jeeves to Spring MVC, we also document services and agree on a common structure for the API.

It looks good ! I put some comments / random thoughs inlined in the document ; the autogenerated api doc looks also nice, and will probably makes the development easier on the project (currently grepping the entry points / opening several files before being actually able to find the corresponding java class for a controller).

Regards,

– Pierre