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=10550>. 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=10550 Delegate path-management to ActionForwards Summary: Delegate path-management to ActionForwards Product: Struts Version: Nightly Build Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Controller AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The ActionForward class could be extended so that paths are generated from dicrete properties. <forward name="SomeAction" path="/someAction" action="true" /> The getPath method would return /do/someAction or /someAction.do, as appropriate. If action were false, it would just return the path verbatim. The developer would not need to know or care what url-pattern is being applied to the application or module. Likewise, the ActionForward could know that its part of a module, and how to handle its module-prefix. (The controller could set this property automatically.) So given the equivalent of <forward name="SomeAction" path="/someAction" action="true" module-prefix="module1" context-prefix="/do" context-suffix="" /> The ActionForward could return /do/module1/someAction given the same thing but changing context-prefix="" context-suffix=".do" the ActionForward could return /module1/someAction.do If it were not an action, and were a page, it could return /module1/someAction.jsp To give people a leg-up on the WEB-INF issues, there could be page-prefix attribute <forward name="SomeAction" path="/someAction" action="true" module-prefix="module1" context-prefix="" context-suffix=".do" page-prefix="/WEB-INF" /> that would result in something like /WEB-INF/module1/someAction.jsp The "WEB-INF" variation might be a standard deviation, as we do with ActionMappings (session vs request). An enhanced ActionForward could also provide a uri-templates capability that would allow developers to generate different paths based on locale or browser type. Ideally, the uri-template feature could assume the responsiblity for the $A$P type patterns now in use. References: http://nagoya.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED] g&msgId=385238 http://www.mail-archive.com/[email protected]/msg04010.html -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
