Hi all,
Currently workspace styles can’t be accessed from global endpoints (outside of the style’s workspace), even when using the workspace qualified style names. To duplicate, using the release data change the tiger_road style to the tiger workspace, and then try to load a tile using the global WMS and the qualified style name:
http://localhost:8080/geoserver/wms?service=WMS&version=1.1.0&request=GetMap&layers=tiger:tiger_roads&styles=tiger:tiger_roads&bbox=-74.02722,40.684221,-73.907005,40.878178&width=317&height=512&srs=EPSG:4326&format=image%2Fjpeg
Workspace layers can be globally accessed using the workspace qualifier; shouldn’t styles work the same way? I can take a stab at updating the DefaultCatalogFacade if the list agrees this behavior should be implemented.
Thanks,
Shane
–
Shane StClair
Software Engineer
Axiom Consulting & Design
http://www.axiomalaska.com
Hi Shane,
This was actually done intently. The reason why we don’t apply the same rule for layers is for backwards compatibility. But I agree it is confusing. It gets more confusing when you start to consider layer groups (which would have to be changed as well to match styles) since they actually reference other resources in the namespace.
That said if you want to poke around at changing the behaviour the class you will need to look at is LocalWorkspaceCatalog.
-Justin
···
On Fri, Feb 22, 2013 at 10:36 PM, Shane StClair <shane@anonymised.com> wrote:
Hi all,
Currently workspace styles can’t be accessed from global endpoints (outside of the style’s workspace), even when using the workspace qualified style names. To duplicate, using the release data change the tiger_road style to the tiger workspace, and then try to load a tile using the global WMS and the qualified style name:
http://localhost:8080/geoserver/wms?service=WMS&version=1.1.0&request=GetMap&layers=tiger:tiger_roads&styles=tiger:tiger_roads&bbox=-74.02722,40.684221,-73.907005,40.878178&width=317&height=512&srs=EPSG:4326&format=image%2Fjpeg
Workspace layers can be globally accessed using the workspace qualifier; shouldn’t styles work the same way? I can take a stab at updating the DefaultCatalogFacade if the list agrees this behavior should be implemented.
Thanks,
Shane
–
Shane StClair
Software Engineer
Axiom Consulting & Design
http://www.axiomalaska.com
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Ok, thanks for the explanation. If it was intentional I’ll leave it be for now, because it’s not preventing any functionality that I really need.
-Shane
···
On Mon, Feb 25, 2013 at 7:29 AM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Hi Shane,
This was actually done intently. The reason why we don’t apply the same rule for layers is for backwards compatibility. But I agree it is confusing. It gets more confusing when you start to consider layer groups (which would have to be changed as well to match styles) since they actually reference other resources in the namespace.
That said if you want to poke around at changing the behaviour the class you will need to look at is LocalWorkspaceCatalog.
-Justin
–
Shane StClair
Software Engineer
Axiom Consulting & Design
http://www.axiomalaska.com
On Fri, Feb 22, 2013 at 10:36 PM, Shane StClair <shane@anonymised.com> wrote:
Hi all,
Currently workspace styles can’t be accessed from global endpoints (outside of the style’s workspace), even when using the workspace qualified style names. To duplicate, using the release data change the tiger_road style to the tiger workspace, and then try to load a tile using the global WMS and the qualified style name:
http://localhost:8080/geoserver/wms?service=WMS&version=1.1.0&request=GetMap&layers=tiger:tiger_roads&styles=tiger:tiger_roads&bbox=-74.02722,40.684221,-73.907005,40.878178&width=317&height=512&srs=EPSG:4326&format=image%2Fjpeg
Workspace layers can be globally accessed using the workspace qualifier; shouldn’t styles work the same way? I can take a stab at updating the DefaultCatalogFacade if the list agrees this behavior should be implemented.
Thanks,
Shane
–
Shane StClair
Software Engineer
Axiom Consulting & Design
http://www.axiomalaska.com
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.