Hi List,
we'd like to configure a pregeneralized feature store without publishing
the postgis datastore and layers pointing the xml configuration directly to
a properties file with the JDBC/JNDI configuration.
This is the GEOSERVER_DATA_DIR/gdata/gadm/gadm.xml :
-----------------------------
<?xml version="1.0" encoding="UTF-8"?>
<GeneralizationInfos version="1.0">
<GeneralizationInfo dataSourceName="file:gdata/gadm/gadm.properties"
featureName="gadm36_0_3857" baseFeatureName=$
<Generalization dataSourceName="file:gdata/gadm/gadm.properties"
distance="5000" featureName="gadm36_0_3857" g$
<Generalization dataSourceName="file:gdata/gadm/gadm.properties"
distance="10000" featureName="gadm36_0_3857" $
<Generalization dataSourceName="file:gdata/gadm/gadm.properties"
distance="25000" featureName="gadm36_0_3857" $
<Generalization dataSourceName="file:gdata/gadm/gadm.properties"
distance="50000" featureName="gadm36_0_3857" $
</GeneralizationInfo>
...
</GeneralizationInfos>
-------------------------------
Close to that file we've also the
GEOSERVER_DATA_DIR/gdata/gadm/gadm.properties
-------------------------------
SPI=org.geotools.data.postgis.PostgisNGDataStoreFactory
host=XXXXX
port=XXXX
database=XXX
schema=gadm
user=XXX
passwd=XXX
Loose\ bbox=true
Estimated\ extends=false
validate\ connections=true
Connection\ timeout=10
preparedStatements=true
-------------------------------
Now the store has been created and we see the list of layers to publish.
When we try to publish a layer we get in the logs
(GEOTOOLS_DEVELOPER.level):
-------------------------------
2020-06-03 16:11:40,557 INFO [org.geoserver.data.gen.DSFinderRepository] -
Not in Geoserver catalog: file:gdata/gadm/gadm.properties
-------------------------------
Seems that the attribute dataSourceName is not recognized as path but as
store name.
Other tests we did with not success:
- all the possible path combinations (f.e. the full path or the local one
./ ) but nothing.
- use a JNDI configuration
The JDBC configuration is correct (we've checked it dozen of thimes)
The gadm.xml file is correct (we've used it with same tables publishing the
feature store and pointing to it as source).
Any known issue about that or evident mistake? We are getting crazy...
Thank you,
Carlo
--
Mr. Carlo Cancellieri
*skype*: ccancellieri
*Twitter*: @cancellieric
*LinkedIn*: http://it.linkedin.com/in/ccancellieri/
_______________________________________________
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
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users