[
https://issues.apache.org/jira/browse/TAP5-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-1373:
---------------------------------
Labels: bulk-close-candidate (was: )
This issue has been last updated more than a year ago, affects an old version
of Tapestry that is not actively developed anymore, and is therefore prone to
be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry (5.4-beta-35, which is available from Maven Central), please update it
as soon as possible. In the case of a feature request, please discuss it with
the Tapestry developer community on the [email protected] mailing list
first.
> @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)
