[JBoss JIRA] Created: (SEAMFACES-57) Use InputElement<T> instead of @InputField for injection of form input
10:09 p.m.
Use InputElement<T> instead of @InputField for injection of form input
----------------------------------------------------------------------
Key: SEAMFACES-57
URL: https://jira.jboss.org/browse/SEAMFACES-57
Project: Seam Faces
Issue Type: Feature Request
Components: Validation & Conversion
Affects Versions: 3.0.0.Beta1
Reporter: Dan Allen
Priority: Minor
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 provide use the narrowing
bean facility in Weld Extensions to make the producer stronger 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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:31 p.m.
New subject: [JBoss JIRA] Updated: (SEAMFACES-57) Use InputElement<T> instead of @InputField for injection of form input
[
https://jira.jboss.org/browse/SEAMFACES-57?page=com.atlassian.jira.plugin...
]
Dan Allen updated SEAMFACES-57:
-------------------------------
Description:
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.
was:
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 provide use the narrowing
bean facility in Weld Extensions to make the producer stronger 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.
Use InputElement<T> instead of @InputField for injection of
form input
----------------------------------------------------------------------
Key: SEAMFACES-57
URL: https://jira.jboss.org/browse/SEAMFACES-57
Project: Seam Faces
Issue Type: Feature Request
Components: Validation & Conversion
Affects Versions: 3.0.0.Beta1
Reporter: Dan Allen
Priority: Minor
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:19 p.m.
New subject: [JBoss JIRA] Updated: (SEAMFACES-57) Use InputElement<T> instead of @InputField for injection of form input
[
https://issues.jboss.org/browse/SEAMFACES-57?page=com.atlassian.jira.plug...
]
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
1:28 p.m.
New subject: [JBoss JIRA] Assigned: (SEAMFACES-57) Use InputElement<T> instead of @InputField for injection of form input
[
https://issues.jboss.org/browse/SEAMFACES-57?page=com.atlassian.jira.plug...
]
Brian Leathem reassigned SEAMFACES-57:
--------------------------------------
Assignee: José Freitas (was: Brian Leathem)
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: José Freitas
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
12:21 a.m.
New subject: [JBoss JIRA] Updated: (SEAMFACES-57) Use InputElement<T> instead of @InputField for injection of form input
[
https://issues.jboss.org/browse/SEAMFACES-57?page=com.atlassian.jira.plug...
]
Brian Leathem updated SEAMFACES-57:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/seam/faces/pull/15
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: José Freitas
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
11:09 p.m.
New subject: [JBoss JIRA] Updated: (SEAMFACES-57) Use InputElement<T> instead of @InputField for injection of form input
[
https://issues.jboss.org/browse/SEAMFACES-57?page=com.atlassian.jira.plug...
]
Brian Leathem updated SEAMFACES-57:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
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: José Freitas
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
10:36 a.m.
New subject: [JBoss JIRA] Commented: (SEAMFACES-57) Use InputElement<T> instead of @InputField for injection of form input
[
https://issues.jboss.org/browse/SEAMFACES-57?page=com.atlassian.jira.plug...
]
José Freitas commented on SEAMFACES-57:
---------------------------------------
I just want to mention that's not an "instead" option. we can now work with
@InputField and InputElement<T>
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: José Freitas
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
5500
days inactive
5626
days old
6 comments
3 participants
participants (3)
-
Brian Leathem (JIRA) -
Dan Allen (JIRA)
-
José Freitas (JIRA)