QUESTION: Is there any way to prevent access to base <action> configuration extended by another <action> within the struts configuration?
CONTEXT: I am looking to setup a template <action> configuration to be used by several actions, however the only way to reference the template <action> is via the "path" attribute. The biggest problem with this is that I don't want the template web accessible and couldn't find a way to prevent the access to the template. Thoughts? Thanks for your time, Andrew --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org