You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org> on 2005/06/21 17:30:17 UTC
[jira] Created: (TAPESTRY-350) RequirableField vs. ValidatableField
RequirableField vs. ValidatableField
------------------------------------
Key: TAPESTRY-350
URL: http://issues.apache.org/jira/browse/TAPESTRY-350
Project: Tapestry
Type: Improvement
Components: Framework
Versions: 4.0
Reporter: Howard M. Lewis Ship
Not completely satisfied with RequirableField components (that have to take a required and requiredMessage parameters),
I'd like to see if we could remove Requireable and just have ValidatableField, and make use of the Required Validator.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Assigned: (TAPESTRY-350) RequirableField vs. ValidatableField
Posted by "Paul Ferraro (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-350?page=all ]
Paul Ferraro reassigned TAPESTRY-350:
-------------------------------------
Assign To: Paul Ferraro
> RequirableField vs. ValidatableField
> ------------------------------------
>
> Key: TAPESTRY-350
> URL: http://issues.apache.org/jira/browse/TAPESTRY-350
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Assignee: Paul Ferraro
>
> Not completely satisfied with RequirableField components (that have to take a required and requiredMessage parameters),
> I'd like to see if we could remove Requireable and just have ValidatableField, and make use of the Required Validator.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Resolved: (TAPESTRY-350) RequirableField vs. ValidatableField
Posted by "Paul Ferraro (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-350?page=all ]
Paul Ferraro resolved TAPESTRY-350:
-----------------------------------
Fix Version: 4.0
Resolution: Fixed
RequirableField interface is now gone. In its place, all formerly requirable fields are now ValidatableFields and can leverage the existing Required validator.
> RequirableField vs. ValidatableField
> ------------------------------------
>
> Key: TAPESTRY-350
> URL: http://issues.apache.org/jira/browse/TAPESTRY-350
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Assignee: Paul Ferraro
> Fix For: 4.0
>
> Not completely satisfied with RequirableField components (that have to take a required and requiredMessage parameters),
> I'd like to see if we could remove Requireable and just have ValidatableField, and make use of the Required Validator.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org