Hi Manfred,
PropertyColumn generates the underlying json using
PropertyResolver.getValue, that's why it works.
ToolbarButton and CommandButton should read directly from the json, and I
didn't thought about sub-expressions.
Please open an issue (and specify the version you are using). The fix is
st
Hi Sebastien.
Sebastien wrote
>> where "data.id" is a valid property to the data of the row.
> Actually, I think "id" is more valid.
The path to by model data id is in second level.
That's why "data.id". For the PropertyColumn/IdPropertyColumn that worked
fine.
Couldn't understand thus why the C
Hi Manfred,
> where "data.id" is a valid property to the data of the row.
Actually, I think "id" is more valid.
CommandButton and ToolbarButton are designed to return the row property
value(s), if supplied. If not supplied, the default property for
CommandButton is "id", and the default for Toolb
On Feb 19, 2017 10:35 AM, "Manfred Bergmann"
wrote:
Solved. Problem was access to the model data
Without more details it is hard to say what is inconsistent and how it
could be improved!
Interestingly though that the PropertyColumn could access the data but the
CommandButton not.
Not sure abo
Solved. Problem was access to the model data.
Interestingly though that the PropertyColumn could access the data but the
CommandButton not.
Not sure about the internals but that's not a consistent behavior.
Manfred
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Kend
