tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2111) ZoneRefresh doesn't document/declare its 'refresh' event
Date Tue, 03 Jun 2014 15:07:01 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016589#comment-14016589
] 

ASF subversion and git services commented on TAP5-2111:
-------------------------------------------------------

Commit 24d47d1a2ea7f6c79d215cd98c38a0ff66c0d3eb in tapestry-5's branch refs/heads/master from
[~jkemnade]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=24d47d1 ]

TAP5-2111: Improve ZoneRefresh javadoc, point out that is triggers the 'refresh' event.


> ZoneRefresh doesn't document/declare its 'refresh' event
> --------------------------------------------------------
>
>                 Key: TAP5-2111
>                 URL: https://issues.apache.org/jira/browse/TAP5-2111
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3.6, 5.4
>            Reporter: Michael Prescott
>            Assignee: Jochen Kemnade
>            Priority: Minor
>              Labels: documentation, newbie
>             Fix For: 5.4
>
>
> The ZoneRefresh component documentation doesn't mention the 'refresh' event, so it's
not apparent that there's any way to override the way it handles refreshing the zone.
> As per Lance Java:
> Far from being a gory detail, it's part of the public API for the mixin,
> very similar to AutoComplete's "provideCompletions" event.
> The mixin should ideally declare the event using @Events("refresh") and
> should have a mention in the javadoc too.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message