Support of getting and setting properties customly in PropertyResolver#74
Support of getting and setting properties customly in PropertyResolver#74PhantomYdn wants to merge 2 commits intoapache:masterfrom
Conversation
Test custom GetAndSetters for PropertyResolver
|
It would be nice if you could file in a ticket in JIRA so that it can be catched up by the Wicket Dev's. For more information take a look here: https://cwiki.apache.org/confluence/display/WICKET/Contributing+to+Wicket |
|
I'm working on a different solution, please take a look at https://github.com/apache/wicket/tree/WICKET-5623-extensible-propertyresolver |
|
Looks interesting and promising:) And what's target release? I hope that some 7.XX? |
Please open a separate issue for that. I'm planning this change for 6.x, 7.x and 8.x |
|
Also - it will be very helfull to make getObjectWithGetAndSet public. Sometimes it's usefully to introspect object by wicket utilities. We switched in Orienteer from spring bean introspection to wicket due not accurate working with beans in Spring (for example if there is a class with methods like: public String getValue(); public void setValue(Object value) - Spring is failing measurably even if property "value" was not directly requested). |
|
Please close this pull request: WICKET-5623 adds IPropertyLocator. |
|
Thanks for implementation of this feature! |
4 participants
There is no way to customize getting of properties from the object. All possible ways to gain properties are hardcoded in PropertyResolver.
But, for example, there is set of NoSQL document DBs which have some class "Document" to work with DB. And to get some property of that document you should call something like this: 'doc.getProperty("myPropertyName")'.
This pull request enables possibility to specify custom GetAndSet for your type of object. Please take a look to PropertyResolverTest