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.
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
smithkm@anonymised.com