Hi Andrea,
I'll look at the DispatcherCallback and GeoServerFilter. For reference the
code is up on as a pull request for inspection…
https://github.com/geoserver/geoserver/pull/330
Tom
On Sep 13, 2013, at 2:32 PM, Andrea Aime wrote:
> On Fri, Sep 13, 2013 at 12:58 PM, Justin Deoliveira
Hi Justin,
Thanks, for the response. I wanted to use the "interceptor" element which
exists in an alternate namespace. The interceptor registration method
available with the DTD style requires nesting under each Mapping instance, with
some mapping instances being outside the WMS module ("/**
On Fri, Sep 13, 2013 at 12:58 PM, Justin Deoliveira wrote:
> Hey Tom,
>
> Afaik in the past the pattern has been when a new module is added (mostly
> extensions and community modules) if the author decides to use the new xsd
> style they can. And I don't know of any ill side affects of doing so. B
Hey Tom,
Afaik in the past the pattern has been when a new module is added (mostly
extensions and community modules) if the author decides to use the new xsd
style they can. And I don't know of any ill side affects of doing so. But
as for porting existing modules to the xsd style not sure that has
Hi Devs,
I am looking at GEOS-6006 and want to use Springs MVC's interceptors to
implement a quick fix (the longer term fix will require some discussion on the
this list).
In order the register the interceptor in the WMS module's
applicationContext.xml I need to update from the 2.x based DTD
