Sorry for bombarding with two proposals at once (actually there could be a third by end of week :o ) … but it has been a bit of a mad rush to get all of this stuff in for 2.2.
Feedback much appreciated. Thanks!
-Justin
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Sorry for bombarding with two proposals at once (actually there could be a third by end of week :o ) ... but it has been a bit of a mad rush to get all of this stuff in for 2.2.
Feedback much appreciated. Thanks!
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
We covered some of this in an earlier discussion; with respect to GSIP a workspace could “override” a global style.
If an additional “point” style is added to the “foo” workspace it acts as an override: a request against the virtual “foo” endpoint, /geoserver/foo.wms?request=GetCapabilities would result in all the global styles (i.e. “point”), plus the ones local to foo (i.e. “point” and “line”) resulting in GetCapabilities with the styles “point”, and “line”.
–
Jody Garnett
On Tuesday, 21 February 2012 at 1:45 PM, Justin Deoliveira wrote:
Hi all,
I would like to put two (somewhat related) proposals up for discussion.
The first adds the ability to store styles and layer groups within a workspace, rather than globally:
Sorry for bombarding with two proposals at once (actually there could be a third by end of week :o ) … but it has been a bit of a mad rush to get all of this stuff in for 2.2.
Feedback much appreciated. Thanks!
-Justin
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d
On Tuesday, 21 February 2012 at 5:31 PM, Jody Garnett wrote:
Evening Justin:
We covered some of this in an earlier discussion; with respect to GSIP a workspace could “override” a global style.
If an additional “point” style is added to the “foo” workspace it acts as an override: a request against the virtual “foo” endpoint, /geoserver/foo.wms?request=GetCapabilities would result in all the global styles (i.e. “point”), plus the ones local to foo (i.e. “point” and “line”) resulting in GetCapabilities with the styles “point”, and “line”.
–
Jody Garnett
On Tuesday, 21 February 2012 at 1:45 PM, Justin Deoliveira wrote:
Hi all,
I would like to put two (somewhat related) proposals up for discussion.
The first adds the ability to store styles and layer groups within a workspace, rather than globally:
Sorry for bombarding with two proposals at once (actually there could be a third by end of week :o ) … but it has been a bit of a mad rush to get all of this stuff in for 2.2.
Feedback much appreciated. Thanks!
-Justin
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d
Yeah, I think i remember. The answer is essentially no, there is no notion of an override at this time, although it is a cool idea. Essentially if you try to create a style or layer group specific to a workspace that already exists globally you will get an exception from the catalog complaining that it already exists.
However you can have two styles named identically as long as they are not in the same workspace, and neither of them is global.
Overrides are a bit tricky since the whole local workspace scheme works by simply filtering out parts of the catalog, and is not much more complex than that. I like the idea but unless there is a big objection i would like to push it off as a future improvement.
We covered some of this in an earlier discussion; with respect to GSIP a workspace could “override” a global style.
If an additional “point” style is added to the “foo” workspace it acts as an override: a request against the virtual “foo” endpoint, /geoserver/foo.wms?request=GetCapabilities would result in all the global styles (i.e. “point”), plus the ones local to foo (i.e. “point” and “line”) resulting in GetCapabilities with the styles “point”, and “line”.
–
Jody Garnett
On Tuesday, 21 February 2012 at 1:45 PM, Justin Deoliveira wrote:
Hi all,
I would like to put two (somewhat related) proposals up for discussion.
The first adds the ability to store styles and layer groups within a workspace, rather than globally:
Sorry for bombarding with two proposals at once (actually there could be a third by end of week :o ) … but it has been a bit of a mad rush to get all of this stuff in for 2.2.
Feedback much appreciated. Thanks!
-Justin
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d