Prefer @Property on @Entity metamodel generation about metagen HOT 4 OPEN

This is not going to be doable, because MetaModel is just a PropertyModel that gives you a typesafe way to build up a property string. Wicket will then interpret that property string to use accessor methods. There is no way via the property expression to indicate that Wicket should use fields vs. accessor methods.

from metagen.

So rewrite the MetaModel class to incorporate useful bits of
PropertyModel and create a flag on SingularProperty that indicates a
preference for the field vs the method(s).

Or change the MetaModel / PropertyModel implementation to inspect the
return type of the getter / setter before using it.

On Mon, Apr 30, 2012 at 1:56 PM, David Hosier
[email protected]
wrote:

This is not going to be doable, because MetaModel is just a PropertyModel that gives you a typesafe way to build up a property string. Wicket will then interpret that property string to use accessor methods. There is no way via the property expression to indicate that Wicket should use fields vs. accessor methods.

---

Reply to this email directly or view it on GitHub:
#7 (comment)

from metagen.

this would require writing our own property resolving mechanism. the one inside wicket is not meant to be extensible because it is optimized.

from metagen.

• Type of Property needs to take into account the type of field or getter based on the preferred one
• Property already has get(instance) method, it will need to be tweaked to take the preference of getter/field into account
• MetaModel's get/set methods will need to split the property expession and loop over each segment calling the correct Property's get/set methods depending on whether or not getObject or setObject is called.
• The traversal in MetaModel will have to safely handle nulls in getObject

from metagen.