[jira] Closed: (STR-1891) Populating attribute values from beans

["Paul Benedict (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/struts/browse/STR-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Benedict closed STR-1891.
------------------------------

    Resolution: Incomplete
      Assignee:     (was: Struts Developers)

No follow-up from reporter.

> Populating attribute values from beans
> --------------------------------------
>
>                 Key: STR-1891
>                 URL: https://issues.apache.org/struts/browse/STR-1891
>             Project: Struts 1
>          Issue Type: Improvement
>          Components: Taglibs
>    Affects Versions: 1.1.0
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Bob Hablutzel
>            Priority: Minor
>
> Consider a highly variable JSP, where some or all of the characteristics of a 
> particular HTML element are variable. In this case, there will be a number of 
> attributes whose values are expressed as a runtime expression, rather than 
> directly:
>    <html:text name="<%= bean.getName() %>"
>               property="<%= bean.getProperty() %>"
>               value="<%= bean.getValue() %>"
>               onchange="<%= bean.getOnchange() %> />
> and so forth.
> I'm proposing adding a new attribute which specifies the attribute values 
> through a standard Java bean. The attribute names would be matched to bean 
> properties, and any matching non-null values would be used as the attribute 
> value. Attribute values not specified in the bean or on the tag would default. 
> It's somewhat arbitrary whether attributes specified both in the tag and the 
> bean would be taken from the bean or tag, but that should be specified.
> The proposed enhancement would allow the above to be written:
>     <html:text propertyBean="bean"/>

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