Uwe Schäfer schrieb:
To me this does not feel like necessarily the right behaviour. I do not see a tremendous advantage in this resolving being done lazily.
for the record: we could change to doing it non-lazy, but it does not solve this particular issue, as the value of public field is constant, depending on the point in time where the CGLib-subclassing happened.
and as we cannot intercept field access... cu uwe --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
