AFAIK I should have a block like <security-constraint> <web-resource-collection> <web-resource-name> province </web-resource-name> <url-pattern> /province.do </url-pattern> <http-method>GET</http-method> <http-method>POST</http-method> </web-resource-collection> <auth-constraint> <role-name>admin</role-name> </auth-constraint> </security-constraint>
For every module I have in my application, isn't it?
This is now officially off-topic, but what do you mean by "module"?
The most common way to do this is partition your application so that URL's that are secured differently have a different prefix, "/admin/*" for example (so, view the prefix as the "module" in your case). I would personally never put <anything>.do in a security constraint since that is too tightly coupled with struts-config and such. I do it by path prefixes. Struts supports this prefixing with its concept of "module", I believe, however I've not used that feature of it.
Erik
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
