[
https://issues.apache.org/jira/browse/WICKET-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860551#comment-15860551
]
Pedro Santos commented on WICKET-6318:
--------------------------------------
The property expression resolver resolution logic was moved to a configurable
implementation of IPropertyExpressionResolver. The current resolver is now the
OGNLPropertyExpressionResolver, and the new one will be implemented using the
parser described in the ticket WICKET-4008 in PropertyExpressionResolver class.
List of changes:
ApplicationSettings --> holds a IPropertyExpressionResolver
PropertyResolver implementation --> OGNLPropertyExpressionResolver
PropertyExpressionResolver --> created to be placeholder for the new property
expression resolver that will work using parsed input
PropertyResolver reflection utility code --> moved to ReflectionUtility
PropertyResolver API --> IPropertyExpressionResolver
IPropertyLocator --> renamed to IPropertyResolver
PropertyResolver.IGetAndSet --> moved to the reflection package
IPropertyReflectionAwareModel --> removed since it's an unused and untested
interface that was breaking AbstractPropertyModel coherence by adding methods
that weren't meant to be an abstraction of the model property, but rather a
reflection API utility that already exists in Wicket's API
PropertyResolver static API --> kept as a faced for now
> 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)
