[
https://issues.apache.org/jira/browse/TAP5-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643258#action_12643258
]
Howard M. Lewis Ship commented on TAP5-266:
-------------------------------------------
This is doable, it's just a matter of significantly reorganizing the way we
generate the invocations of the render phase methods. We really need to be
able to match methods to phases all at once, to ensure that each method is
slotted to only one phase (AfterRender for the example in the issue).
Currently we do the BeginRender processing, then later the AfterRender
processing, and the method gets slotted into each.
> When component render phase annotation is used the method name should be
> ignored
> --------------------------------------------------------------------------------
>
> 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
> Priority: Minor
>
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
