[seam-issues] [JBoss JIRA] Updated: (SEAMFACES-57) Use InputElement<T> instead of @InputField for injection of form input

Brian Leathem (JIRA) jira-events at lists.jboss.org
Thu Feb 24 17:19:06 EST 2011


     [ https://issues.jboss.org/browse/SEAMFACES-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated SEAMFACES-57:
-----------------------------------

         Assignee: Brian Leathem
    Fix Version/s: 3.0.0.Final


> Use InputElement<T> instead of @InputField for injection of form input
> ----------------------------------------------------------------------
>
>                 Key: SEAMFACES-57
>                 URL: https://issues.jboss.org/browse/SEAMFACES-57
>             Project: Seam Faces
>          Issue Type: Feature Request
>          Components: Validation & Conversion
>    Affects Versions: 3.0.0.Beta1
>            Reporter: Dan Allen
>            Assignee: Brian Leathem
>            Priority: Minor
>             Fix For: 3.0.0.Final
>
>
> The idea for @InputField is nice, but having access to only the converted value of a field is limiting. We should switch to a wrapper type at the injection point to provide access to the id, clientId and component. The implementation could also leverage the narrowing bean facility in Weld Extensions to make the producer more strongly typed.
> Proposal:
> @Inject
> private InputElement<String> firstName;
> @Inject
> private InputElement<String> lastName;
> @Inject
> private InputElement<Date> dateOfBirth;
> InputElement<T>
>    String id
>    String clientId
>    T value
>    UIInput component
> The input element thus allows much more flexibility in terms of what the developer can accomplish in the validation method. One of those is being able to assign a message to a particular input field.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list