Hi,
as reported in http://jira.codehaus.org/browse/GEOS-4421 the current automatic
filter integration with the spring context is causing trouble in security land,
making it impossible to disable spring security, causing potential
ordering issues
in the filter execution and doubling up the security filters work.
What about having SpringDelegatingFilter look for a specific marker interface
for filters that we wish to be integrated, instead of just picking any Filter?
Something like:
/**
* Interface implemented by filters that want to be plugged into the
* web request processing by simple declaration into the Spring context
*/
interface GeoServePluginFilter extends Filter {
}
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 333 8128928
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
