Thanks Jean! Your solution worked out really well! Merci encore, Pierric
Le mer. 9 sept. 2020 à 22:47, Jean Pommier <jean.pomm...@pi-geosolutions.fr> a écrit : > Hi Pierric, > > I'd say this is related to the encryption of the postgis password. You'll > have to redefine it. It has already happened to me. > > I'm doing this by memory, but I think it should work : > > 1) go to the folder of your postgis datastore > > 2) remove, in datastore.xml the line about the password > > 3) reload geoserver > > the datastore should be visible now. Just open it and set the password. It > should be enough to get back all your layers > > > Best, > > Jean > > *Jean Pommier -- pi-Geosolutions* > > Ingénieur, consultant indépendant > > Tél. : (+33) 6 09 23 21 36 > E-mail : j...@pi-geosolutions.fr > Web : www.pi-geosolutions.fr > Le 09/09/2020 à 21:04, Pierric de Laborie a écrit : > > Hello, > > I installed the version 2.17.1 of Geoserver and moved my "workspaces" > folder (from version 2.16.2) to the data folder, hoping that Geoserver > would recognize all my layers. It did well for all the layers based on > files (shapefiles and rasters). > However the other vector layers based on a Postgis store were not > recognized. The Postgis store was not recognized either. I tried to > recreate a Postgis store with the exact same definition (name) successfully > and restarted the Geoserver but it didn't help to recognize all the xml > layer definitions located in the same folder as the store definition (in > workspaces folder). > Is there any way to avoid publishing explicitly every Postgis layer again? > > Thanks! > Pierric > > > _______________________________________________ > 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 > > Geoserver-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/geoserver-users > > _______________________________________________ > 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 > > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users >
_______________________________________________ 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
