[
https://issues.apache.org/jira/browse/TAP5-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797446#action_12797446
]
Howard M. Lewis Ship commented on TAP5-266:
-------------------------------------------
I only fixed this for render phase events; I may need to apply the same
technique to life cycle events. I don't think this will affect event handler
methods, but I'm not sure.
> In a conflict between a render phase annotation and the naming convention,
> the explicit annotation should win
> -------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-266
> URL: https://issues.apache.org/jira/browse/TAP5-266
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.15
> Reporter: Hugo Palma
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.2.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
