Hi Christian, What are your plans for moving your module to an extension or core? It would be nice if this was done before we start patching web.xml to handle the request mapping. That said, I understand that that is a big hurdle for such a small patch... so it is not a -1, just a comment/question.
An alternative would be to come up with a generic "/security" mapping in web.xml, and have your mapping declared in your applicationContext.xml, mapping it to "security/geoxaml". Not sure if this makes sense for you, but it would allow you to do your "routing" in your plugin, rather than in the core. Having a root "security" context would also make sense if we foresee future security plugins which will have servlets/controllers similar to the geoxacml one. 2c, -Justin Christian Müller wrote: > Hi Andrea, it would be time to > > 1) apply the patch > 2) creating an offical subdir "geoxacml" in the web2 geoserver data dir. > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
