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.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|17d 5h 22m||1||Howard M. Lewis Ship||07/Nov/08 23:27|
|46m 50s||1||Howard M. Lewis Ship||08/Nov/08 00:14|
|Status||In Progress [ 3 ]||Closed [ 6 ]|
|Resolution||Fixed [ 1 ]|
|Fix Version/s||5.0.16 [ 12313427 ]|
|Summary||When @Property generated accessor methods will overwrite user generated accessors then either warn the user or do not generate them.||When using the @Property annotation, Tapestry should throw an exception rather than overwrite an existing method|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Field||Original Value||New Value|
|Assignee||Howard M. Lewis Ship [ hlship ]|