tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-1373) @PageActivationContext should case the activate event to be aborted
Date Tue, 29 Dec 2015 10:19:49 GMT

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

Jochen Kemnade closed TAP5-1373.
--------------------------------
    Resolution: Incomplete

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4
preview release), feel free to provide the necessary information and reopen.

> @PageActivationContext should case the activate event to be aborted
> -------------------------------------------------------------------
>
>                 Key: TAP5-1373
>                 URL: https://issues.apache.org/jira/browse/TAP5-1373
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2
>            Reporter: Igor Drobiazko
>            Assignee: Igor Drobiazko
>              Labels: bulk-close-candidate
>
> Currently it is not possible to have both: a field annotated with @PageActivationContext
and a no-args onActivate() method. The generated method doesn't abort the event, so that the
no-args activation method is called afterwards. This behaviour overrides the activation context
retrieved from the URL.
> public class Foo {
>    @PageActivationContext
>    private String bar; 
>    void onActivate() {
>        bar = "baz";
>    } 
> }
> The generated method should store a "true" result in order to abort the event.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message