The WMS capabilities doc for a workspace virtual service will show layer groups in the global workspace. GetMap requests made against them through the virtual service will fail though.
A comment in LocalWorkspaceCatalogFilter suggests that the layer appearing in the capabilities is intentional. https://github.com/geoserver/geoserver/blame/master/src/main/src/main/java/org/geoserver/ows/LocalWorkspaceCatalogFilter.java#L85 Depending on how you come at it, either could be counter-intuitive. That the global workspace is "global" suggests that it's contents should be inherited by other workspaces, while virtual services being specific to workspaces suggests that they should only provide what's in the workspace. I think GEOS-5238 is (or at least includes) the same issue. The specific error has changed from "Could not find layer" to "No layers have been requested" though. -- Kevin Michael Smith [email protected] ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
