[
https://issues.apache.org/jira/browse/PIVOT-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055694#comment-13055694
]
Greg Brown commented on PIVOT-761:
----------------------------------
>>Perhaps, but then the user could bypass the validation by invoking the setter
>>directly.
>Yes is true, but It is the same that property binding. If you call a setter
>directly nobody is notified of the change.
Not sure what type of property binding you are referring to, but all Pivot bean
properties fire change events.
> I think that you like declaring validations at UI level instead of data level.
Not necessarily. I think that certain validations make sense in the bean
itself, but others may be more appropriate for the UI to perform.
> Test a more generic Validation approach on fields and Containers (Forms, etc)
> -----------------------------------------------------------------------------
>
> Key: PIVOT-761
> URL: https://issues.apache.org/jira/browse/PIVOT-761
> Project: Pivot
> Issue Type: Brainstorming
> Components: wtk
> Reporter: Sandro Martini
> Assignee: Sandro Martini
> Priority: Minor
> Fix For: 2.1
>
>
> Investigating on this field ... both on validating single fields (not only
> text input fields) and Container (like Forms), like in JSF.
> Some reference here:
> http://apache-pivot-developers.417237.n3.nabble.com/Text-validators-td3078385.html
> General idea: put investigation code under /skunk and the minimal set of
> interfaces and classes, and the rest outside (in a dedicated subproject, here
> or under apache-extras).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
