That might be true, we 'solved' the issue by simply using the afterRender in the child class. According to the documentation under:http://tapestry.apache.org/component-rendering.html the following is written:
Parents before Child Ordering is always parent-first. Methods defined in the parent class are always invoked before methods defined in the child class. When a sub-class overrides an render phase method of a base class, the method is only invoked once, along with any other base class methods. The subclass can change the implementation of the base class method via an override, but can't change the timing of when that method is invoked. See TAPESTRY-2311. This is not true, at least when using @Import -- View this message in context: http://tapestry.1045711.n5.nabble.com/Inheritance-and-the-order-of-loaded-JS-tp5714430p5714500.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
