Added my +1 to the proposal, it is good functionality that will be very
much appreciated.

In terms of user interface change, I was wondering if the "WMS Settings"
would be disabled (or hidden) if the WMS service was not turned on? If so
it may be more consistent to use a checkbox (as with enabling/disabling
tile services, enabling/disabling workspace WMS, enabling/disabling global
WMS.

I know user interface consistently is far down the list of priorities :P
--
Jody Garnett


On Mon, 19 Nov 2018 at 06:42, Andrea Aime <andrea.a...@geo-solutions.it>
wrote:

> On Tue, Nov 13, 2018 at 10:28 PM <br...@frogmouth.net> wrote:
>
>> +1 on the concept.
>>
>>
>>
>> Is there a plan for a REST API for this?
>>
>
> The proposal highlights two new properties for LayerInfo. As LayerInfo is
> serialized to XML by reflection, they will automatically
> end up showing on the REST API outputs. I've added a bit of of text in the
> proposal.
> I also had to move the flags from layer to resource, because the wfs/wcs
> service go directly for the resource skipping the layer configuration.
>
>
>>  For the backwards compatibility problem, I concur with the default
>> approach for an existing data dir (preserve existing behaviour).
>>
>>
>>
>> For the new service part of the problem (“Users plugging-in a new service
>> while selective service configurations are already in place”), you could
>> add a second interface that says whether the new service is enabled or
>> disabled on layers by default. It seems unlikely that most developers would
>> want opt-in for their shiny new service,  so its probably not worth the
>> effort.
>>
>
> Agreed, I believe an admin is in a better position to deal with this.
> Adding a service should be a matter of planning, the admin should be
> able to use the REST API, go through the layers, and change the
> configuration accordingly.
> That said, I've modified the proposal to clarify that.
>
> Cheers
> Andrea
>
> ==
>
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf
> Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa
> (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
> http://www.geo-solutions.it http://twitter.com/geosolutions_it
> ------------------------------------------------------- *Con riferimento
> alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
> Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
> circostanza inerente alla presente email (il suo contenuto, gli eventuali
> allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
> destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
> errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
> sarei comunque grato se potesse darmene notizia. This email is intended
> only for the person or entity to which it is addressed and may contain
> information that is privileged, confidential or otherwise protected from
> disclosure. We remind that - as provided by European Regulation 2016/679
> “GDPR” - copying, dissemination or use of this e-mail or the information
> herein by anyone other than the intended recipient is prohibited. If you
> have received this email by mistake, please notify us immediately by
> telephone or e-mail.*
> _______________________________________________
> 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

Reply via email to