struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Benedict (JIRA)" <>
Subject [jira] Closed: (STR-1114) [taglib] html:form uses 'action' not 'input' to select mapping, etc.
Date Tue, 13 Nov 2007 08:22:36 GMT


Paul Benedict closed STR-1114.

    Resolution: Won't Fix

> [taglib] html:form uses 'action' not 'input' to select mapping, etc.
> --------------------------------------------------------------------
>                 Key: STR-1114
>                 URL:
>             Project: Struts 1
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: Nightly Build
>         Environment: Operating System: All
> Platform: All
>            Reporter: Hakan Soderstrom
>            Priority: Minor
> Package org.apache.struts.taglib.html, subsection "About the form tag".
> Hope I'm getting this right, not too experienced with Struts, reading the doco
> with microscope to get my app working.
> (1) Paragraph "The name of the bean and its class can be specified as a property
> to the form tag..." This (i.e. the 'name' and 'type' attributes) is deprecated
> as of 1.1b3 according to the taglib reference.
> (2) Same paragraph. "If the current page is specified as the input property for
> an action, the name of the action is used." Inspecting
> I get the impression that the
> 'action' attribute is used to find a mapping. The 'input' attribute is not used
> at all for this purpose, as far as I can see. Test runs confirm that the mapping
> with a path that agrees with the 'action' attribute is selected. 'Agrees' means
> that the extension may be chopped off.
> (3) Same paragraph: "the name of the action is used." Extend the sentence to
> include "as the name attribute of the generated HTML <FORM> tag". Vital information.
> (4) The example after 'Here's a clip from the Struts Example configuration:'.
> The struts-config DTD requires that 'form-beans' precedes 'action-mappings'. The
> two should be swapped (as they indeed are in the real example configuration).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message