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/07/01 19:43:00 UTC
[jira] Created: (TAPESTRY-369) Allow update of invalid form submit data
Allow update of invalid form submit data
----------------------------------------
Key: TAPESTRY-369
URL: http://issues.apache.org/jira/browse/TAPESTRY-369
Project: Tapestry
Type: New Feature
Components: Framework
Versions: 4.0
Reporter: Howard M. Lewis Ship
Fix For: 4.0
The current form element components (TextField, ValidField, etc.) that support validation will not update bound properties if there is a validation error.
This is not always desirable.
When building a multi-page wizard, you will often allow the user to move backwards and forwards through the wizard.
It is disconcerting to move backwards and then forwards and NOT see a value for a field at all, just because it failed some validation constraints.
Now, ideally, we should be able to come back to the page and have those fields decorated and errors marked ... but that is well beyond the capabilities of the current system.
Hm. An interesting idea; the validation delegate could track component addresses (page name + id path) and corresponding names. It could then *restore* names, even on a subsequent render of an otherwise fresh page. A wizard would have a seperate delegate for each page in the wizard and the wizard would persist between requests.
--
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-369) Allow update of invalid form submit data
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-369?page=all ]
Howard M. Lewis Ship resolved TAPESTRY-369:
-------------------------------------------
Resolution: Invalid
Working my problem a bit more, I found that by making the validaton delegate persistent AND by keeping a seperate delegate for each form (that is, each page in my multi-page wizard) I was able to get the exact behavior I wanted.
> Allow update of invalid form submit data
> ----------------------------------------
>
> Key: TAPESTRY-369
> URL: http://issues.apache.org/jira/browse/TAPESTRY-369
> Project: Tapestry
> Type: New Feature
> Components: Framework
> Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Fix For: 4.0
>
> The current form element components (TextField, ValidField, etc.) that support validation will not update bound properties if there is a validation error.
> This is not always desirable.
> When building a multi-page wizard, you will often allow the user to move backwards and forwards through the wizard.
> It is disconcerting to move backwards and then forwards and NOT see a value for a field at all, just because it failed some validation constraints.
> Now, ideally, we should be able to come back to the page and have those fields decorated and errors marked ... but that is well beyond the capabilities of the current system.
> Hm. An interesting idea; the validation delegate could track component addresses (page name + id path) and corresponding names. It could then *restore* names, even on a subsequent render of an otherwise fresh page. A wizard would have a seperate delegate for each page in the wizard and the wizard would persist between requests.
--
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