hi kevin,it is currenly not possible to read the parameters of a component from within a mixin. i filed a jira entry some time ago... feel free to vote for it :)https://issues.apache.org/jira/browse/TAPESTRY-1764g,kris-robert zeigler <[EMAIL PROTECTED]> schrieb: -An: "Tapestry users" Von: R
Hi Kevin,
I wonder if you could use mixin parameters for this?
Since the value to be operated on is likely to have different names
for different components (certainly no guaranteed name), it seems like
specifying a mixin parameter which tapestry will "autobind" is perhaps
the way to go?
Th
