Hello,
I have a workspace in GeoServer with a certain structure. When I look at the geoserver directories; all stores, layers and styles are stored relative to the workspace directory.
What I would like to do is copy this workspace structure. Why? Because all workspaces will contain exactly the same structure, it is just that I restrict my users to their own workspace so they only see the objects that are relevant to them.
-
Is it possible to copy the structure? I’ve been trying, but it seems to fail on all id’s
-
Are the ID’s like NamespaceInfoImpl–403b0cfd:13fa9e64852:-7fff bound to a certain format? Or can I overwrite them with my own? And if so, should they be unique geoserver wide, or simply within their parent (like for instance within the workspace)
Thanks in advance,
Milo
On Thu, Jul 18, 2013 at 9:16 AM, Milo van der Linden <milo@anonymised.com>wrote:
Hello Justin,
- Is it possible to copy the structure? I've been trying, but it seems to
fail on all id's
We actually do this a lot in order to modularize geoserver
configurations. It is actually one of the driving things behind supporting
workspace local styles and layer groups. But basically it requires all
references to be local to the workspace. One common issue is with layers
that use the default global styles. Those will be different on a different
configuration.
Everything within the workspace dir is local. I made sure there are no
references that depend on the global styles.
Do you know specially where references are failing?
- Are the ID's like
<id>NamespaceInfoImpl--403b0cfd:13fa9e64852:-7fff</id> bound to a certain
format? Or can I overwrite them with my own? And if so, should they be
unique geoserver wide, or simply within their parent (like for instance
within the workspace)
No specific format is required so you can rewrite them but they must be
globally unique within that server.
That is where they fail, if I copy dir "myworkspace_1" to "myworkspace_2"
do I need to go through all the files to change the id's in "myworkspace_2"
to prevent conflicts with "myworkspace_1"?
You shouldn't have to no, because those ids should have been generated
with a UUID in the first place and should be universally unique. ALthough
until recently I think perhaps we only used a UID which guarantees
uniqueness on a single host. So if it is an older configuration then i
guess there is a chance of conflict.
Thanks in advance,
Milo
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.