tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Hennebrueder (JIRA)" <j...@apache.org>
Subject [jira] Updated: (TAP5-831) Record errors for beaneditform and form using only the field name instead of injecting a field (patch incl)
Date Wed, 02 Sep 2009 08:12:32 GMT

     [ https://issues.apache.org/jira/browse/TAP5-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sebastian Hennebrueder updated TAP5-831:
----------------------------------------

    Attachment: beaneditform.patch

Patch against 810243

> 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
>         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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message