You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/05/27 09:20:54 UTC

[jira] [Updated] (TAP5-1319) Need to support property paths for validated field

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

Jochen Kemnade updated TAP5-1319:
---------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> Need to support property paths for validated field
> --------------------------------------------------
>
>                 Key: TAP5-1319
>                 URL: https://issues.apache.org/jira/browse/TAP5-1319
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-beanvalidator
>    Affects Versions: 5.2
>            Reporter: Vladimir Velikiy
>              Labels: bulk-close-candidate
>         Attachments: ImprovedBeanFieldValidator.java, RequiredContext.java, RequiredContextImpl.java, propertyPathSupport.diff
>
>
> Current implementation does not support property paths for beans, while the Bean Validation API and Hibernate Validator support this feature.
> In attachment my own implementation of BeanFieldValidator.java with support this feature as well as isRequired() method.



--
This message was sent by Atlassian JIRA
(v6.2#6252)