Thanks for the pointer. I didn't find that issue when looking for something similar.
Davor Hrg wrote: > I've created a minimaly invasive patch for this some time ago, > https://issues.apache.org/jira/browse/TAPESTRY-2116 > > it only requires notion of transformable methods for ClassTransformation > so any field access inside them gets transformed.... > > I've been patching tapestry with it since, because I use it in my apps > all the time, > > no one is forced to use this, and of course it is useless for properties > used in unit tests... but I really do not want to test my local variable > used in loop.... > > It's not like I couldn't live without it .... > why is it so wrong to use this ? > > Davor Hrg > > On 3/1/08, Filip S. Adamsen <[EMAIL PROTECTED]> wrote: > >> Yeah, I tend to break up big pages into smaller components, especially >> if I can get any re-use out of it, which - it turns out - I often can. >> >> -Filip >> >> César Lesc skrev: >> >>> May be is a sign that you need to refactor your class because is >>> getting too many responsibilities. :) >>> >>> César. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > >
