[TAP5-301] When using the @Property annotation, Tapestry should throw an exception rather than overwrite an existing method

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.15
• Fix Version/s: 5.0.16
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Joel Halbert
• Created: 21/Oct/08 18:04
• Updated: 08/Nov/08 00:14
• Resolved: 08/Nov/08 00:14

Description

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.