[
https://issues.apache.org/jira/browse/WICKET-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864936#comment-15864936
]
Pedro Santos commented on WICKET-6318:
--------------------------------------
Hi Sven,
ObjectWithGetAndSet is the replacement, it provides the same metadata.
wicket-bean-validation works by reading *only* reflection metadata, which
AbstractPropertyModel won't always provide. To implement any reflection API
will be a plain false promise to wicket-bean-validation.
e.g.: a new IPropertyExpressionResolver that resolve expressions for
'JSONObject's is set in the application. From this point one, any
PropertyExpression/AbstractPropertyModel object will start to resolve
expression to ObjectWithGetAndSet that set/get objects by using a JSON API
rather than the reflection one.
I gave more reasons for the removal in my first comment as well.
> To make PropertyResolver a configurable implementation
> ------------------------------------------------------
>
> Key: WICKET-6318
> URL: https://issues.apache.org/jira/browse/WICKET-6318
> Project: Wicket
> Issue Type: Sub-task
> Components: wicket
> Reporter: Pedro Santos
>
> To enable users to select each property resolver will be used, so if the new
> implementation shows problematic it can be switched back to the a Wicket's <
> 7 one.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
