Josh Canfield wrote: > > > Thiago is right. Currently the way this works is an implementation > detail and not a documented feature so you end up setting yourself up > for much pain if it stops working that way in the future... Maybe we > can document the order libraries are loaded, or something to make this > a supported feature.... > >
I wasn't aware of the "@Submodule" and "auto-loading" logic in term of module loading order. I remember I had the same issue [1] and I had to implement a decorator for the ComponentClassResolver service to modify the module loading order (using java reflection: ugly but no better solution found at that moment [2]). I still think that it could be very interresting to handle ordered lists for ComponentClassResolver contributions to provide GUI extensibility. [1] http://www.mail-archive.com/users@tapestry.apache.org/msg43088.html [2] http://www.mail-archive.com/users@tapestry.apache.org/msg34196.html Nourredine. -- View this message in context: http://old.nabble.com/Complex-Question-about-Templates-and-Inheritance-tp28858822p28870316.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
