Hi team, I moved the current property expression resolution logic to OGNLPropertyExpressionResolver and made it a configurable option at the application, so we have a room for new property expression resolvers like the one using a parser. I also made some code cleanup like removing IPropertyReflectionAwareModel and moved some methods with no internal state their own utility class so they can be used by anyone needing to get the same class metadata via reflection.
The work is just in its initial state, but I pushed it anyway to share my idea and to get your input on it. You can check it at the branch "WICKET-6318-configurable-property-expression-resolver" and I add more detailed description of the changes at the ticket WICKET-6318 Cheers Pedro Santos 1 - https://github.com/apache/wicket/tree/WICKET-6318-configurable-property-expression-resolver 2 - https://issues.apache.org/jira/browse/WICKET-6318
