I think I've seen messages on the mailing lists about problems related to multiple onActivate's a long time ago.
https://issues.apache.org/jira/browse/TAPESTRY-1730 seems to suggest that the method with the most parameters is called first, but whether the execution stops here or continues to the next onActivate I don't know... In any case I would go with Lance' suggestion and stick with a single onActivate; in that case it is clear what the method does and evaluation order is not an issue (if it ever was). -- Chris On Wed, Sep 10, 2014 at 11:01 AM, Lance Java <lance.j...@googlemail.com> wrote: > No, this is a new feature. > > Your onActivate methods are very complex. Have you considered a single > onActivate(EventContext)? > > Perhaps the '-' in '-3' is just a presentation issue. > > I think the main culprit is likely to be your onPassivate(). Does it return > all 3 objects (when populated). >
