[Geoserver-users] REST API: layers with the same name from different workspaces

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 also interact with the individual ws-prefixed layer (add/remove styles etc.).

Am I trying to do something that is currently not possible at all?

···

Alessandro Pasotti
w3: www.itopen.it

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 Pasotti <apasotti@anonymised.com> wrote:

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 also interact with the individual ws-prefixed layer (add/remove styles etc.).

Am I trying to do something that is currently not possible at all?

Alessandro Pasotti
w3: www.itopen.it



Geoserver-users mailing list
Geoserver-users@anonymised.com.382…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

==
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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.


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 roads

there is no way to tell them apart

···

On Tue, Aug 16, 2016 at 11:25 AM, Andrea Aime <andrea.aime@anonymised.com.1107…> wrote:

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 Pasotti <apasotti@anonymised.com> wrote:

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 also interact with the individual ws-prefixed layer (add/remove styles etc.).

Am I trying to do something that is currently not possible at all?

Alessandro Pasotti
w3: www.itopen.it



Geoserver-users mailing list
Geoserver-users@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

==
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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.


Alessandro Pasotti
w3: www.itopen.it

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 materialized), but with today’s arrangement it’s a problem.

Imho it would make more sense to have the list of layers inside each workspace instead, of course that would cause
backwards compatibility issues, but for some time I guess we could simply have both, and qualify the ones at the global level.
Anyways, just my opinion, it’s probably something worth discussing in the devel list once there are funds to tackle it.

In the meantime I’d open a bug report here (adding the prefix in the name element is not that hard, what I describe above
is certanly more work instead):
https://osgeo-org.atlassian.net/projects/GEOS/summary

Cheers
Andrea

···

On Tue, Aug 16, 2016 at 11:42 AM, Alessandro Pasotti <apasotti@anonymised.com> wrote:

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 roads

there is no way to tell them apart

On Tue, Aug 16, 2016 at 11:25 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

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

Alessandro Pasotti
w3: www.itopen.it

On Tue, Aug 16, 2016 at 10:16 AM, Alessandro Pasotti <apasotti@anonymised.com> wrote:

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 also interact with the individual ws-prefixed layer (add/remove styles etc.).

Am I trying to do something that is currently not possible at all?

Alessandro Pasotti
w3: www.itopen.it



Geoserver-users mailing list
Geoserver-users@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

==
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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.


==
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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.


Done: https://osgeo-org.atlassian.net/browse/GEOS-7682

Cheers

···

On Tue, Aug 16, 2016 at 11:52 AM, Andrea Aime <andrea.aime@anonymised.com.1107…> 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 workspace (we were supposed to have a concept of “Map”
that would have held layers, and no global layers, but that that never materialized), but with today’s arrangement it’s a problem.

Imho it would make more sense to have the list of layers inside each workspace instead, of course that would cause
backwards compatibility issues, but for some time I guess we could simply have both, and qualify the ones at the global level.
Anyways, just my opinion, it’s probably something worth discussing in the devel list once there are funds to tackle it.

In the meantime I’d open a bug report here (adding the prefix in the name element is not that hard, what I describe above
is certanly more work instead):
https://osgeo-org.atlassian.net/projects/GEOS/summary

Cheers

Andrea

On Tue, Aug 16, 2016 at 11:42 AM, Alessandro Pasotti <apasotti@anonymised.com> wrote:

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 roads

there is no way to tell them apart

==
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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.


On Tue, Aug 16, 2016 at 11:25 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

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

Alessandro Pasotti
w3: www.itopen.it

On Tue, Aug 16, 2016 at 10:16 AM, Alessandro Pasotti <apasotti@anonymised.com> wrote:

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 also interact with the individual ws-prefixed layer (add/remove styles etc.).

Am I trying to do something that is currently not possible at all?

Alessandro Pasotti
w3: www.itopen.it



Geoserver-users mailing list
Geoserver-users@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

==
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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.


Alessandro Pasotti
w3: www.itopen.it