Or have the parent class invoke a "placeholder" method that is overridden in the subclass to add further scripts after the base class has added its scripts. Part of the design of Tapestry is that it does not force you to use specific base classes, so you are free to design your own that fit your needs.
On Thu, Jul 12, 2012 at 7:31 AM, Lance Java <lance.j...@googlemail.com> wrote: > This sounds familiar... I think that the solution was to use different render > phases to control the ordering of imports. Instead of putting @Import > statements at the class level, put them on render phase methods (eg > setupRender and beginRender) to control the ordering. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Inheritance-and-the-order-of-loaded-JS-tp5714430p5714433.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 > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
