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=10268>. 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=10268 Sub-apps need context-relative option for 'input' of an Action [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2002-07-05 22:19 ------- I believe the functionality just checked in (available in nightly build 20020706), coupled with recent changes, addresses this use case. Now, you can use a combination of the following mechanisms: * Set the "forwardPattern" property on the <controller element to "/WEB-INF/pages$A$P", so that the URIs for forwards will be computed according to this pattern. Change the paths on existing <forward> elements to remove the "/WEB-INF/pages" prefix. * Set the "inputForward" property on the <controller> element to "true", to indicate that the "input" attribute on an <action> should be considered to be the name of a local or global <forward>, instead of a subapp-relative URI (which remains the default for backwards compatibility). Create new forwards and adjust existing "input" attributes as needed for this. Now, mapping for input pages is done the same as for other forwards, and you can use the "store JSP pages under WEB-INF" pattern successfully even with subapps. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
