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)" <ji...@apache.org> on 2011/09/23 20:06:28 UTC

[jira] [Updated] (TAP5-1339) Provide a single extension point to provide a ValidationDecorator instance for both traditional and Ajax renders

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

Howard M. Lewis Ship updated TAP5-1339:
---------------------------------------

    Summary: Provide a single extension point to provide a ValidationDecorator instance for both traditional and Ajax renders  (was: ValidationDecorator doesn't get called when form is rendered for zone update)

I've really changed this ... your problem is (I'm assuming) that you overrode Tapestry's use of DefaultValidationDecorator for traditional requests, but not for Ajax requests.

I've introduce a new service, ValidationDecoratorFactory, that can be overridden to catch both cases.

> Provide a single extension point to provide a ValidationDecorator instance for both traditional and Ajax renders
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1339
>                 URL: https://issues.apache.org/jira/browse/TAP5-1339
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2.3
>            Reporter: Hugo Palma
>            Priority: Minor
>             Fix For: 5.3
>
>
> I contributed a custom ValidationDecorator which works fine when the form is rendered as part of the normal page render lifecycle.
> But, if i update a zone with the same form component the ValidationDecorator doesn't get executed and as such the form doesn't get decorated.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira