You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/09/07 13:32:00 UTC

[jira] [Commented] (TAP5-2692) Create support for static activation context values for event handler methods

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

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

Commit b58a865881495f4494909029614b6d180182eec1 in tapestry-5's branch refs/heads/rest from Thiago H. de Paula Figueiredo
[ https://gitbox.apache.org/repos/asf?p=tapestry-5.git;h=b58a865 ]

TAP5-2692: @StaticActivationContextValue


> Create support for static activation context values for event handler methods
> -----------------------------------------------------------------------------
>
>                 Key: TAP5-2692
>                 URL: https://issues.apache.org/jira/browse/TAP5-2692
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>            Reporter: Thiago Henrique De Paula Figueiredo
>            Assignee: Thiago Henrique De Paula Figueiredo
>            Priority: Major
>
> This way, we can have more than one event handler in the same class with the same parameters, but different names, and let Tapestry choose the appropriate one instead of having a single event handler method that needs have logic to do different things for different values of activation context values. This can be pretty useful for implementing multiple REST endpoints in the same class in the future.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)