On Fri, Jun 29, 2012 at 9:51 AM, Andrea Aime <[email protected]> wrote: > On Fri, Jun 29, 2012 at 2:49 PM, Andrea Aime <[email protected]> > wrote: >> >> Hi, >> I've just tested for the first time in years the behavior of the "wms >> path" setting in GeoServer. >> Capabilities wise it seems to be working, if I set "/sf" as the wms path >> for all the spearfish layers >> they are correctly placed inside a "sf" layer inside the capabilties >> document (thus generating >> a proper tree). >> >> However if I ask for the layer "sf" on a GetMap I get a service exception. >> Is it just me, or in that >> case we would be supposed to paint a map with all the layers under "sf"? > > > Looking at the code it also seems that this was the behavior before Gabriel > big wms refactor > (http://jira.codehaus.org/browse/GEOS-2652), there is a "// pre > GEOS-2652" commented > out section of code that does just that, scan all the layers and find those > that are under the > sf path... > I see. I don't remember why that got commented out and not ported. May just be an overlook. In any case I don't think the wmspath approach will work for most cases when you need to call a parent layer by name. Reason is because there's no way to specify the order in which the nested layers are to be drawn, so assuming it's gonna be on alphabetical order seems just too hacky. Also don't think it'll work if you have more than one level of nesting. Or perhaps yes, as layer names shall be unique, but at the very least the regular expression used to match the wmspaths (in the commented out code) should be smarter to avoid matching both "sf" and "sfxxx".
This is related to something I guess Martin Davis was wondering about some time ago. And at that time we thought providing LayerGroups a flag indicating whether to expose it's list of layers as nested on the capabilities would work. Things may get tricky though and a simple flag may not suffice. What if you have the nested layer also exposed as a top level one? In any case, I think it's not the first time people is looking for layer grouping in capabilities, and perhaps we could get to an easy enough solution that preserves the rendering order and allows for calling a parent layer by name by a) letting layer groups advertise its children in getcaps, b) allowing layergroups be child of layergroups. Thoughts? Cheers, Gabriel > Cheers > Andrea > > -- > Ing. Andrea Aime > GeoSolutions S.A.S. > Tech lead > > Via Poggio alle Viti 1187 > 55054 Massarosa (LU) > Italy > > phone: +39 0584 962313 > fax: +39 0584 962313 > mob: +39 339 8844549 > > http://www.geo-solutions.it > http://geo-solutions.blogspot.com/ > http://www.youtube.com/user/GeoSolutionsIT > http://www.linkedin.com/in/andreaaime > http://twitter.com/geowolf > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > -- Gabriel Roldan OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
