tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (TAP5-266) When component render phase annotation is used the method name should be ignored
Date Wed, 06 Jan 2010 20:41:54 GMT

     [ https://issues.apache.org/jira/browse/TAP5-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship reassigned TAP5-266:
-----------------------------------------

    Assignee: Howard M. Lewis Ship

> 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
>            Assignee: Howard M. Lewis Ship
>            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.


Mime
View raw message