[
https://issues.apache.org/jira/browse/TAP5-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade closed TAP5-831.
-------------------------------
Resolution: Invalid
We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the
latest 5.4 preview release), feel free to provide the necessary information and
reopen.
> Record errors for beaneditform and form using only the field name instead of
> injecting a field (patch incl)
> -----------------------------------------------------------------------------------------------------------
>
> Key: TAP5-831
> URL: https://issues.apache.org/jira/browse/TAP5-831
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.2
> Reporter: Sebastian Hennebrueder
> Labels: bulk-close-candidate
> Attachments: beaneditform.patch
>
>
> In order to record an error for a field using custom validation, currently
> you have to use t:parameter to define a custom input field inside of
> beaneditform
> and inject that field into your page class.
> The provided patch adds a method
> recordError(String fieldname, String errorMessage) to beaneditform, form and
> validation tracker to allow using just the fieldname or id.
> A test is included and I build a sample application using this approach. I
> didn't want to extend the existing test apps as it was unclear to me where to
> my code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
