[TAP5-266] In a conflict between a render phase annotation and the naming convention, the explicit annotation should win

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.0.15
• Fix Version/s: 5.2.0
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Hugo Palma
• Created: 13/Oct/08 10:16
• Updated: 07/Jan/10 02:05
• Resolved: 07/Jan/10 02:04

Description

If i have a method like this:

@AfterRender
void beginRender()
{
}

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.