[
https://issues.apache.org/jira/browse/WICKET-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868590#comment-15868590
]
Pedro Santos commented on WICKET-6318:
--------------------------------------
> Yes, this is what WICKET-5623 is about.
Sure, my point is: if application's IPropertyLocator does return an IGetAndSet
providing a Field or a Method, it will be wrong given that no Field nor Method
exists for an unique property expressed in a JSONObject.
> So what? From IPropertyReflectionAwareModel's Javadoc: "It is valid to return
> null for any method".
In fact *all* IPropertyReflectionAwareModel's methods Javadoc says "I may not
have reflection information". We can even rename it to maybe/possibleAwareModel
> I don't understand this sentence
I just realized that I misunderstood you. I thought you talking about models
with lazy loading of their objects.
>I've just tested the identical setup for LazyModel and it works perfectly. Why
>shouldn't it?
I'm not familiar with LazyModel, will take a better look since the new
IPropertyExpressionResolver should enable it work fine without
IPropertyReflectionAwareModel.
> 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)
