This is kind of tricky as general problem - how do we manage configuration files such as required for templates, icons, app-schema mapping configuration, pregeneralized datastore config etc...
I think we have now isolated all file access to ResourceStore API <https://github.com/geoserver/geoserver/wiki/ResourceStore-API-Examples> - and I had hoped to see a simple REST API added to manage configuration objects such as this. -- Jody -- Jody Garnett On 10 June 2015 at 08:53, stefano.costa <stefano.co...@geo-solutions.it> wrote: > Dear all, > I'm working on automating the creation/update of app-schema datastores in > GeoServer leveraging the REST API. > The current API already allows the creation of an app-schema datastore > and, of course, it is already possible to create secondary > namespaces/workspaces via REST: what is missing (at least AFAIK) is the > possibility to upload an app-schema mapping file to an already created > app-schema datastore (also creating a new one based on the uploaded mapping > file would be nice). > > I had a quick look at the REST endpoints we already have and I focused on > this one: > /workspaces//datastores//[file|url|external][.extension] > <http://docs.geoserver.org/stable/en/user/rest/api/datastores.html#workspaces-ws-datastores-ds-file-url-external-extension> > > which is ultimately handled by either DataStoreFileResource or > CoverageStoreFileResource. The supported extensions so far are shape, > properties, h2 and spatialite. > > I'm proposing to add a new extension, appschema, that will be handled by a > new kind of resource, let's call it AppSchemaDataAccessResource, extending > StoreFileResource, which will take care of copying the uploaded mapping > file to its proper location. > I'm a bit puzzled as to where (i.e. in which module) this new class should > be put: I guess gs-restconfig would be the wrong place, since it would make > it dependent on gt-app-schema. Perhaps the best way would be to create a > new module, let's call it gt-app-schema-rest, containing just > AppSchemaDataAccessResource and occasional supporting classes, and then > have StoreFileFinder (gs-restconfig module) somehow look it up dynamically. > > Any thoughts/suggestions? > > Thanks! > > Best regards, > Stefano Costa > > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > Dott. Stefano Costa > Senior Software Engineer > > GeoSolutions S.A.S. > Via Poggio alle Viti 1187 > 55054 Massarosa (LU) > Italy > phone: +39 0584 962313 > fax: +39 0584 1660272 > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > ------------------------------------------------------- > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. > Il loro utilizzo è consentito esclusivamente al destinatario del > messaggio, per le finalità indicate nel messaggio stesso. Qualora > riceviate questo messaggio senza esserne il destinatario, Vi preghiamo > cortesemente di darcene notizia via e-mail e di procedere alla > distruzione del messaggio stesso, cancellandolo dal Vostro sistema. > Conservare il messaggio stesso, divulgarlo anche in parte, > distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità > diverse, costituisce comportamento contrario ai principi dettati dal > D.Lgs. 196/2003. > > The information in this message and/or attachments, is intended solely > for the attention and use of the named addressee(s) and may be > confidential or proprietary in nature or covered by the provisions of > privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New > Data Protection Code).Any use not in accord with its purpose, any > disclosure, reproduction, copying, distribution, or either > dissemination, either whole or partial, is strictly forbidden except > previous formal approval of the named addressee(s). If you are not the > intended recipient, please contact immediately the sender by > telephone, fax or e-mail and delete the information in this message > that has been received in error. The sender does not give any warranty > or accept liability as the content, accuracy or completeness of sent > messages and accepts no responsibility for changes made after they > were sent or for other risks which arise as a result of e-mail > transmission, viruses, etc. > > > ------------------------------------------------------------------------------ > > _______________________________________________ > 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
