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=7202>. 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=7202 Add forward attribute to FormTag to allow submision to a global forward ------- Additional Comments From [EMAIL PROTECTED] 2002-07-03 10:08 ------- [Another use-case occurred to me, so I'd thought I'd document all three.] A few use cases to consider: (-1-) Presents a unified API to page designers. If ActionForwards could be used with the html:form tag, page designers could work from a single logical command set rather than two (ActionForwards and Actions). In practice, many ActionForwards are used with query strings, and the html:link tags encourages this, making ActionForwards the equivalent of type=GET forms. (-2-) Permits reuse of pages using the html:tag. If the target action for a page could changed at runtime, by passing a different local ActionForward, then the same page could be used in different workflows. Many pages can be used to either add or update a model state. But since to share the presentation page we need to share the ActionMapping, developers have to code their actions around this requirement. If the action for page could be changed, they may prefer to have separate ActionMappings for add and update. Some pages may also be reused in different contexts. A search page may contain common parameters that can be used to search different sets of records,but each set of records may be controled by a different Action. Any given page might be used independantly or in a larger workflow, which implies it needs to be submitted to different ActionMappings at different times. There are workarounds for all these circumstnaces, but a forward option to the html:form tag would eliminate the need for these workarounds and encourage cleaner, kludge-free APIs that will be easier for page designers to use. Alternatives like the DispatchAction. (-3-) Consistent use with inputForward. The ActionMapping.inputForward property will often lead back to another ActionMapping, so JavaBeans that populate any of the controls can be recreated. This will lead to more global ActionForwards being created to represent ActionMappings. In the same workflow, Developers will then be referring to the same action in two different ways, here through it's Action URI, there through it's ActionForward name. If forwards can be used in html:form, developers have the opportunity to use a unified API namespace. The inputForward property also implies that different ActionMappings could specify different local forwards. However, this feature would be more useful html:form could also use a local forward and make it easier to reuse presentation pages, in the same way that we can reuse Actions. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
