If i have a method like this:
it actually gets executed twice. Once during AfterRender and once during BeginRender. Although i agree that is bad coding it can cause some confusion and make it hard to diagnose.
In my opinion there should be either an error thrown by Tapestry in this situation or it should just ignore the method name when a render phase annotation is present.
Also, i didn't try if this also happens for component events.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|450d 14h 13m||1||Howard M. Lewis Ship||07/Jan/10 00:29|
|1h 35m||1||Howard M. Lewis Ship||07/Jan/10 02:04|
|Status||In Progress [ 3 ]||Closed [ 6 ]|
|Fix Version/s||5.2.0 [ 12314122 ]|
|Resolution||Fixed [ 1 ]|
|Summary||When component render phase annotation is used the method name should be ignored||In a conflict between a render phase annotation and the naming convention, the explicit annotation should win|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Assignee||Howard M. Lewis Ship [ hlship ]|
|Field||Original Value||New Value|
|Priority||Major [ 3 ]||Minor [ 4 ]|