DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16603>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16603 <controller> forwardPattern should support different module roots. [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Enhancement |Normal ------- Additional Comments From [EMAIL PROTECTED] 2003-02-06 08:57 ------- I'm not sure to understand you well... It's not true that forwardPattern does'nt support arbitrary paths. The code of RequestUtils.forwardURL() do it very well and is used in RequestProcessor. So we actualy can (since 1.1b2 at least) define forwardPattern like "/WEB- INF/my_modules/$M$P" and *it works*. The problem is that ActionConfig.forward and ActionConfig.input paths are not processed the same way as ForwardConfig.path. I can't see how it can be an enancment as it's allready implemented and is documented in the user guide : http://jakarta.apache.org/struts/userGuide/configuration.html#controller_config This said, I agree that placing pages under /WEB-INF/ is not portable, and I thank you for your solution. But such a *bug* is not bound to the /WEB-INF/ dir, it will occure with a forwardPattern like "$M/pages/$P" or any else than "$M$P". And if it's the only pattern we can define I don't see what it's made for... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
