> ...by adding @Property you're asking for a getter / setter pair that > are benign in operation and have no side effects whereas your own > getters and setters could do anything. > > If you have a nefarious setter but don't notice it because you were > blinded by the @Property annotation I can foresee bugs creeping into > code which would be hard to track down.
sure, only when you expect that @Property will fail if you already have getter/setter, 5.2 used to overload methods from superclass… anyway you can also mistype onevent method and wondering what went wrong > With live page reloading, surely the time taken to add (write=false) > and click refresh is negligible, no? our app reloads between 10-20seconds so it does matter right now, 5.3 should improve it Denis Oct 18, 2011 v 1:26 PM, Steve Eynon: > > Steve. > > On 18 October 2011 18:35, Denis Stepanov <denis.stepa...@gmail.com> wrote: >> Hi everyone, >> >> when using @Property anotation on a page with existing getter or setter >> Tapestry will throw an exception, would it be better to just ignore adding a >> new method rather than throwing an exception? I don't think it could lead to >> unexpected behavior, there is not so many cases when there is a >> getter/setter in super class, it will save time checking if read/write is >> consistent with getters/setters and fixing unexpected exceptions. >> >> Denis >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org >
