I think you should raise the issue in tap5 not tapestry https://issues.apache.org/jira/browse/TAP5
On Tue, Oct 21, 2008 at 12:33 PM, Joel Halbert <[EMAIL PROTECTED]> wrote: > JIRA raised: https://issues.apache.org/jira/browse/TAPESTRY-2713 > > Joel Halbert wrote: >> >> Hi, >> >> Occasionally I get stung when I declare an @Property on my page and then >> at some point later I create custom accessor methods for the property - >> which of course are never invoked since the @Property generated code wipes >> over them. >> >> I realise this is pretty minor, and all of my own doing, but I think a >> small amount of pain might be saved if T5 either: >> >> a) warns when @Property is declared at the same time as accessor methods >> for the property are defined. >> b) does not generate accessor methods when user defined methods are >> already present. >> >> I know there are options on @Property to circumvent generating accesor >> methods, but this doesn't really help in those cases where you have >> forgotten about the @Property declaration. >> >> If anyone else thinks this might be useful I'll raise a JIRA. >> >> Thx, >> Joel >> > > -- > SU3 Analytics Ltd > 61b Oxford Gardens > W10 5UJ > London > > Tel: +44 20 8960 2634 > Mob: +44 75 2501 0825 > www.su3analytics.com > > SU3 Analytics Ltd is a company registered in England and Wales under company > number 06639473 at registered address 61b Oxford Gardens, London W10 5UJ, > United Kingdom. > > > > --------------------------------------------------------------------- > 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]
