[ https://issues.apache.org/jira/browse/TAP5-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971772#action_12971772 ]
Josh Canfield commented on TAP5-1373: ------------------------------------- This sounds like a feature, not a bug. If you want to do other initialization in onActivate then you should be able to do this. Your example code should be: void onActivate() { if ( bar == null ) bar = "baz"; // Handle other activation stuff } > @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.4 > Reporter: Igor Drobiazko > Assignee: Igor Drobiazko > > 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 is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.