On Sep 19, 2012, at 1:38 PM, Gabriel Roldan <grol...@opengeo.org> wrote:
> On Wed, Sep 19, 2012 at 4:23 AM, Tom Kunicki <tkuni...@usgs.gov> wrote:
>>
>> Hi,
>>
>> I am having an issue with GWC endpoints in GeoServer 2.2 RC-3 ignoring
>> non-default styles.
>>
>> I'm running testing GeoServer 2.2 RC-3 with layer backed by vector data
>> served via GWC endpoints including integrated-WMS and WMS-C. The layer I am
>> testing has 2 available rendering styles. I've setup an openlayers client
>> (based on 2.12) against the endpoints using 3 service options for base
>> layers; WMS (tiled=false), WMS (tiled=true) and WMS-C. As expected the
>> latter 2 endpoints cache as verified by performance and investigation of the
>> HTTP-Response Headers. The issue I have is that the cached endpoints ignore
>> the requested style and always provided tiles rendered with the default
>> style. The WMS (tiled=false) endpoint reacts as expected when the alternate
>> style is requested. The options available per-layer ("Create a separate
>> cache for each STYLE" = true) as well as the option under Caching Defaults
>> ("Automatically cache non-default styles') would seem to indicate that
>> non-default styles would be supported and rendered with the GeoServer/GWC
>> integration where the specification of the service used supports it.
>
> I think that probably auto cache styles may not be enabled for your
> layers? you'd need to check layer by layer, because if those layers
> already existed it is probably not enabled for them?
> the setting in the global gwc settings page affect newly added layers,
> but every layer has its own setting.
Thanks for the response. "Create a separate cache for each STYLE" was true for
the layer in question. Based on your comment I took the following steps in the
layer configuration: disabled caching, saved, reenabled the layer and
per-style caching, saved. Now everything works. This is great, thanks.
I don't know the exact sequence of steps taken to induce my issue, if I can
reproduce I will submit an issue. My workflow thus far has been to work with
the per-layer configuration first, then look at the global cache settings.
Thanks again, Tom.
>
>>
>> I did wipe my GEOSERVER_DATA_DIR after updating to 2.2 RC-3 and setup my
>> workspace, datastore and layers in case there were some vestigial files
>> laying about from older RCs.
>>
>> Thanks,
>>
>> Tom Kunicki
>> Center for Integrated Data Analytics
>> U.S. Geological Survey
>> 8505 Research Way
>> Middleton, WI 53562
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Geoserver-users mailing list
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
>
> --
> Gabriel Roldan
> OpenGeo - http://opengeo.org
> Expert service straight from the developers.
Tom Kunicki
Center for Integrated Data Analytics
U.S. Geological Survey
8505 Research Way
Middleton, WI 53562
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
