[
https://issues.apache.org/jira/browse/TAPESTRY-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-1771.
------------------------------------------
Resolution: Won't Fix
Assignee: Howard M. Lewis Ship
As outlined in the comments, there are numerous work arounds. I wouldn't quite
call this invalid. One possible solution would be to have Tapestry ignore
@Override methods in subclasses when looking for event handler methods.
> Render Phase method called twice when overriding base class method
> ------------------------------------------------------------------
>
> Key: TAPESTRY-1771
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1771
> Project: Tapestry
> Issue Type: Bug
> Affects Versions: 5.0.5
> Reporter: Ted Steen
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.7
>
>
> When implementing a render phase method in a base class (in base package) and
> then overriding it in the extending class (in the page package) the render
> phase method is called twice. Expected behaviour is that it should be called
> once.
> Also if the method in the base class has a different name than the method in
> the extending class, then the annotated method in the base class is called
> _and_ the annotated method in the extending class is called. But maybe this
> is expected behaviour?
--
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]
