+1 Regards, Simone Giannecchini == GeoServer Professional Services from the experts! Visit http://bit.ly/gs-services for more information. == Ing. Simone Giannecchini @simogeo Founder/Director
GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 333 8128928 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. On Tue, Mar 23, 2021 at 1:43 PM Gabriel Roldan <gabriel.rol...@gmail.com> wrote: > Hi list, > > I'm writing to ask for permission to create a new community module for: > - the definition of GeoServer REST API in OpenAPI 3.0 yaml files, > - openapi-generator-maven-plugin generated java client (feign + okhttp) > - Java client wrapper library that simplifies interacting with the > generated client by taking care of wrapping/unwrapping objects between the > mismatching request and response bodies in the current API version. > > The original work comes from this project: > https://github.com/camptocamp/geoserver-rest-openapi > It's been used in production for a while now for an internal c2c project, > and recently adopted by a geOrchestra microservice. > > That said, it's so far only dealing with basic catalog and config objects, > and focuses only on JSON representations. > > The OpenAPI 3.0 definition files are being migrated by hand using the > Swagger 2.0 ones as guidelines, and verified to work and match GeoServer's > request/responses by integration testing. > > Being a pure client, requiring no other geoserver or geotools > dependencies, it comes with its own pure POJO object model for catalog and > config objects, and uses mapstruct to map between this presentation model > and the internal Catalog/Info object model. > > A convenient choice has been made in configuring the object model mapper > so that whenever a change is made to the internal model (e.g. CatalogInfo > class hierarchy), the build will fail on this new module, forcing to keep > them up to date. > > Awaiting your comments/approval. > > Best regards, > -- > Gabriel Roldán > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
