A stakeholder encountered a problem when they created a standard data
store for a geotiff where they used a "folder/filepath" for the data
store name (i.e., they included "/" characters in the name on a
Linux-based system). The system accepted the data store and the user
successfully created and used layers based on the data store. But, upon
restart, the layers and data stores "disappeared" -- they were no longer
accessible nor manifest in the web admin.
Behind the scenes, it appears GeoServer created a folder hierarchy under
the workspaces folder based on "folder/filepath" in the data store
name. At startup, GeoServer did not load the data store from within
this folder hierarchy.
I am assuming the "folder/filepath" is an invalid name. If so, is there
a way to preempt invalid data store names?
--
Bruce Schubert
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
