Closed fxi closed 5 years ago
Hi @fxi hope the year started well for you and your team. i'm going to have a look asap to this, and report to you.
@fxi, @PierreLacroix first apologies for this glitch. This issue escaped to the latest enhancements because of wrong 'vocabulary' I followed and some differences in the Geoserver REST API whether we deal with the global config or the workspace config. Until now, i was thinking that enabling/disabling were operated with an UPDATE operation, which makes senses (in principle), and this is in line with the piece of code you tried.
But I've realized that Geoserver doesn't treat an OGC service enabling/disabling (what we have as checkbox in the Web Interface) in the same way depending if you look at global service or workspace service:
enabled
to false
in the rest config (with no effect on the checkbox). Instead a DELETE operation has to be applied, which deletes the service config. Unfortunately for me, this was not explicitely mentioned in the API doc, and the tests are not able to catch this.I've pushed some fix for this, and tried out on GeoServer 2.14.
It's important that you don't use the updateServiceSettings
method for that, but rather the shortcuts i've put in place such as disableWMS
, disableWFS
, disableWCS
. Depending if you disable a global or workspace setting, geosapi will apply the right operation behind (UPDATE, DELETE).
Let me know
Thanks for this!
To wrap it up, after updating geosapi, enableWxS
for enabling and disableWxS
for disabling. Keep updateServiceSettings
for other settings such as title.
I will look at this tomorrow first thing.
Have a nice evening !
So, I've modified my wrapper/bridge around geosapi
and it seems to work well. Each CRUD operation we do in our app is now fully reproduced in GeoServer through geosapi.
If our "in-depth" tests show something else, I will reopen this issue or create a new one.
Thanks for your efficiency !
You're welcome!
@fxi just to let you know that i've submitted geosapi in CRAN, and it has been accepted for publication. Soon i'll create a tag in github to match this release.
@eblondel Thanks for the notification !
Hi @eblondel,
Hope you started well this year !
I have encountered a small glitch. Maybe it's an misunderstanding of mine :
Should have disabled it, but apparently it doesn't:
Thanks for looking at this.
CC: @PierreLacroix