[
https://issues.apache.org/jira/browse/WICKET-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088617#comment-13088617
]
Martijn Dashorst commented on WICKET-3857:
------------------------------------------
Removing Validatable from wicket core proper is IMO a mistake: the
documentation specifically states that it is a user-space object, there is no
issue with having it remain in core (is it obsolete?) and we really should make
efforts of *deprecating* classes between major releases before removing them
(unless there is no alternative i.e. where the deprecated class would not work).
Unless Igor has specific issue with the class remaining in core, I would like
it to be moved back.
> Allow validators access to component's model
> --------------------------------------------
>
> Key: WICKET-3857
> URL: https://issues.apache.org/jira/browse/WICKET-3857
> Project: Wicket
> Issue Type: New Feature
> Reporter: Igor Vaynberg
> Assignee: Igor Vaynberg
> Fix For: 1.4.18, 1.5-RC6
>
>
> sometimes it is useful for validators to get access to component's model. for
> example
> a) validators can use the model to get value as it was before editing started
> - ie a password validator that forces the user to change their password
> b) validators can access some metadata about the model - ie a model that
> implements IPropertyReflectionAwareModel
> in 1.4 this is done by adding a IModelAwareValidatable#getModel() mixin and
> casting IValidatable down to it. in 1.5 #getModel() has been introduced
> direction to IValidatable
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
