Hi all,
I don't know if this has always been the case but when one starts GeoServer with no styles defined in the catalog, it adds one called "normal", which then all feature types default to when they don't specify other styling information.
But since the style does not actually exist, the feature type becomes invalid and is disabled.
Is this desired behavior?
-Justin
--
Justin Deoliveira
jdeolive@anonymised.com
The Open Planning Project
http://topp.openplans.org
Weird. Probably not exactly the desired behavior. Would it be possible to construct a style in memory called 'normal'? So that things don't fail? It seems like it'd be nice to have some sort of default style, so that quick visualization is always possible.
Chris
Justin Deoliveira wrote:
Hi all,
I don't know if this has always been the case but when one starts GeoServer with no styles defined in the catalog, it adds one called "normal", which then all feature types default to when they don't specify other styling information.
But since the style does not actually exist, the feature type becomes invalid and is disabled.
Is this desired behavior?
-Justin
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
We should be shipping with at minimum the 4 default styles: point, line, polygon, raster. To avoid the issue of no styles being there. But as for the 'normal' style I think one should be created so the feature type will always work.
Brent Owens
(The Open Planning Project)
Justin Deoliveira wrote:
Hi all,
I don't know if this has always been the case but when one starts GeoServer with no styles defined in the catalog, it adds one called "normal", which then all feature types default to when they don't specify other styling information.
But since the style does not actually exist, the feature type becomes invalid and is disabled.
Is this desired behavior?
-Justin
Hmmm, shipping with a bunch of default styles is one thing, but not being able to configure wfs without specifying a default sld is another.
I can see the argument for being able to visualize somethign out of the box, but I can also see the argument for someone just interesting in wfs not wanting to worry about specifying styles.
So yeah, I think Chris's suggestion would be ideal, create an "in memory" style if one is not around, but dont tie it to a file on disk.
Brent Owens wrote:
We should be shipping with at minimum the 4 default styles: point, line, polygon, raster. To avoid the issue of no styles being there. But as for the 'normal' style I think one should be created so the feature type will always work.
Brent Owens
(The Open Planning Project)Justin Deoliveira wrote:
Hi all,
I don't know if this has always been the case but when one starts GeoServer with no styles defined in the catalog, it adds one called "normal", which then all feature types default to when they don't specify other styling information.
But since the style does not actually exist, the feature type becomes invalid and is disabled.
Is this desired behavior?
-Justin
!DSPAM:1004,45d25de3251952081064789!
--
Justin Deoliveira
jdeolive@anonymised.com
The Open Planning Project
http://topp.openplans.org
Ah, I see now what you are getting at. Yeh your idea seems to work: if they want to use wfs alone, the feature type should be valid without a style. Having a 'normal' style in memory should work.
Brent Owens
(The Open Planning Project)
Justin Deoliveira wrote:
Hmmm, shipping with a bunch of default styles is one thing, but not being able to configure wfs without specifying a default sld is another.
I can see the argument for being able to visualize somethign out of the box, but I can also see the argument for someone just interesting in wfs not wanting to worry about specifying styles.
So yeah, I think Chris's suggestion would be ideal, create an "in memory" style if one is not around, but dont tie it to a file on disk.
Brent Owens wrote:
We should be shipping with at minimum the 4 default styles: point, line, polygon, raster. To avoid the issue of no styles being there. But as for the 'normal' style I think one should be created so the feature type will always work.
Brent Owens
(The Open Planning Project)Justin Deoliveira wrote:
Hi all,
I don't know if this has always been the case but when one starts GeoServer with no styles defined in the catalog, it adds one called "normal", which then all feature types default to when they don't specify other styling information.
But since the style does not actually exist, the feature type becomes invalid and is disabled.
Is this desired behavior?
-Justin
!DSPAM:1004,45d25de3251952081064789!