Hi Robert, it's a bug that was fixed, from your description it seems just partially (don't have time to check in detail, sorry...).
In general, to have the remote style work, consistency with the contents of the capabilities documents is required: - If you are using a global service, the capabilities document contains fully qualified layer names, the remote SLD should match. - If you are using a workspace specific service, the capabilities document contains simple names, not prefixed by the workspace name, the remote SLD should also match. Being able to mix-in fully qualified names in a workspace specific service was not meant to work, but unfortunately, it did and some users relied on it. If rasters are behaving differently, it should be fixed for them as well. I'm not against having some settings that reinstate the old, more relaxed behavior, too, as long as it does not make GEOS-10215 regress. PRs welcomed, see the PR template for review and merge rules <https://github.com/geoserver/geoserver/blob/main/.github/PULL_REQUEST_TEMPLATE.md> . Cheers Andrea On Wed, May 25, 2022 at 4:48 PM Robert Goodman <goodm...@us.ibm.com> wrote: > After upgrading to Geoserver 19.6 styles were no longer be applied to > Vector layers but continue to work of Raster layers. We passed the style > descriptor using an URL on the sld parameter. The style descriptor includes > the workspace name as part of the style name. > > > > workspace_name:layer_name > > > > The issue seems to be caused by a change in a file > LocalWorkspaceCatalog.java at line 480 where a call to method wrapNested() > was added. This change meant calls made to get the LayerInfo/ResourceInfo, > the workspace name wasn't returned for Vector layers but is still returned > for Raster layers. Without the workspace name being returned, Geoserver > doesn't match the style and uses the default style. To get around the > problem I set the workspace configuration option "Include Layer Prefix in > Local Workspace Capabilities" in the UI. > > > > The fact that the behavior is different between Vector and Raster layers > seems to be a bug but wanted to ask to make sure. There seems to be 2 > possibilities > > > > 1. I should have always set the "Include Layer Prefix in Local > Workspace Capabilities”, but the option is not being handled correctly for > Raster Layers. It was fixed for Vector layers. > 2. The changed inadvertently broke Vector layers and was intended to > only deal with FeatureTypeInfo. The code is going thru the FeatureTypeInfo > path when handling Vector layers. > > > > Has anybody else ran into this issue? I haven't been able to find any > documentation on the "Include Layer Prefix in Local Workspace Capabilities" > option. > > > > Thanks > > Bob > > > > Robert Goodman – goodm...@us.ibm.com > _______________________________________________ > 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 > -- Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://bit.ly/gs-services-us for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions Group phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 333 8128928 https://www.geosolutionsgroup.com/ 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-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
