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=7276>. 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=7276 html:form and html:link tags need to be able to reference actions outside current sub application [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2002-07-04 02:14 ------- For <html:link>, in additon to Joe's suggestion of using "href", you can also configure the contextRelative property of a <forward> to skip the usual Struts action of prepending the subapp prefix. For <html:link>, you can also forward to an Action that is implemented with org.apache.struts.actions.SwitchAction, which is the formal mechanism for a UI-initiated switch between subapps. For <html:form>, I believe the better way to submit to an action in a different subapplication is something like this (in an Action in the "from" subapp): * Call RequestUtils.selectApplication() to select the "to" subapp you want. * Return an ActionForward from this new subapp that points at a page in the "to" subapp that creates the form you want. * The <html:form> on the new page will automatically be pointing at the "to" subapp. Doing things this way avoids creating deep dependencies between subapps (i.e. a form in one subapp and an action in another would depend on each other), which would make maintenance of different subapps by different groups (a very common scenario) more brittle. The WONTFIX part of the resolution of this bug is about changes to <html:form> -- <html:link> already seems to have the flexibility you need. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
