[
https://issues.apache.org/jira/browse/TAP5-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171345#comment-15171345
]
ASF subversion and git services commented on TAP5-1707:
-------------------------------------------------------
Commit e3c2d044f70739c13fd744cf5c67d8c2aa8d91d8 in tapestry-5's branch
refs/heads/master from [~bobharner]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=e3c2d04 ]
TAP5-1707 javadoc improvements for RenderNotification mixin
> The RenderNotification Mixin should documented with an example
> --------------------------------------------------------------
>
> Key: TAP5-1707
> URL: https://issues.apache.org/jira/browse/TAP5-1707
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Steve Eynon
> Priority: Trivial
> Labels: bulk-close-candidate
>
> The RenderNotification Mixin seems to be an idiomatic way to generate render
> phase 'like' events during an Ajax rendering. But alas the concept is a
> tricky one with a couple of gotchas and could really do with a worked example
> (in the JavaDocs) to fully explain its usage.
> The email thread is :
> http://tapestry.1045711.n5.nabble.com/T5-2-Looking-For-A-RenderNotification-Mixin-Example-td4917771.html
> I've picked out some relevant bits...
> I would like some pre and post render events to be fired on a component after
> it's handled an Ajax event and returned a Zone which it contains.
> <div t:type="Zone" id="zone">
> <div t:type="Any" t:mixins="RenderNotification">
> <!-- zone content ->
> </div>
> </div>
> When the Any component renders as a whole, it receives the render phase
> methods which are picked up the Mixin. The Mixin then fires its own component
> events with the same name, which bubble up the component hierarchy.
> But the beforeRender and afterRender triggered by this mixins are not render
> events, so they should be handled by onBeforeRender[FromComponentId] and
> onAfterRender[FromComponentId] methods or @OnEvent(value = "afterRender",
> component = "id"). In both cases, the component id is optional.
> Nice one - I may have overlooked the onBeginRender() vs beginRender().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
