Done: https://osgeo-org.atlassian.net/browse/GEOS-7682
Cheers
On Tue, Aug 16, 2016 at 11:52 AM, Andrea Aime
wrote:
> Hi,
> yep... the original design concept of layers and resources was quite a bit
> different from what we have today,
> and in that, it made sense not to qualify the layers by w
Hi,
yep... the original design concept of layers and resources was quite a bit
different from what we have today,
and in that, it made sense not to qualify the layers by workspace (we were
supposed to have a concept of "Map"
that would have held layers, and no global layers, but that that never
mat
Thanks for your answer, but I'm afraid I've found a bug in 2.9:
I've configured two layers with the same name 'roads' in two different ws:
'sf' and 'sf2', this is what I get from
http://localhost:8080/geoserver/rest/layers.xml
roads
http://www.w3.org/2005/Atom"; rel="alternate" href="
http://
Ciao Alessandro,
looking at how the code works, I'd say access via qualified name ought to
be working
for all types of requests.
I have tried only with GET, that seems to work as expected.
Let us know if it works out well for you
Cheers
Andrea
On Tue, Aug 16, 2016 at 10:16 AM, Alessandro Pasott
Hi,
I believe this is a known limitation of the REST API, but I wonder if is
there any way to overcome this limitation with some parsing of the XML
results.
You can probably prefix the layers names with the ws to get the layer
details from the REST API but I don't know if that would allow you to
