[
https://issues.apache.org/jira/browse/WICKET-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867577#comment-15867577
]
Sven Meier commented on WICKET-6318:
------------------------------------
> an AbstractPropertyModel/PropertyModel holds a property expression resolving
> a property inside a JSONObject
> (Wicket's custom IPropertyLocator does enable such scenario)
Yes, this is what WICKET-5623 is about.
> IPropertyReflectionAwareModel ... which won't live up since there is no
> reflection information ... about [this] property
So what? From IPropertyReflectionAwareModel's Javadoc: "It is valid to return
null for any method".
>AbstractPropertyModel's IPropertyReflectionAwareModel implementation never
>worked with lazy models
I don't understand this sentence: AbstractPropertyModel's
IPropertyReflectionAwareModel implementation works, and LazyModel's
IPropertyReflectionAwareModel implementation works. There's no cross connection
between the two
>This feature is ... tested at PropertyValidatorRequiredTest ... to detect the
>@NotNull constraint at TestContainedBean.
I've just tested the identical setup for LazyModel and it works perfectly. Why
shouldn't it?
> 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)
