Does Wicket also check for direct public property of the same name ?
not yet, but that is easy to build.
Same remark concerning maps vs beans.
If find it great if we don't know if the property is contained in the
Map or is a property of the Model.
i am alos still in favor the current impl by just doing dots nothing more.
The only thing is that for maps that are also a bean is a bit difficult.
But i find that a bad idea anyway.(a map that is also a bean)
if the object is an instance of a Map:
first try to interpret prop as a Map key
that will never fails (if it is a setter) (mymap.xxx = yyy)
So i think it must be the other way around.
First try to do a setter and then if that fails use it as a map.
