Em Mon, 24 Aug 2009 11:47:47 -0300, Scyta1e <ch...@uzza.net> escreveu:
Specifically the application has 100+ pluggable modules. Each module has it's own jar containing its specific classes and related Tapestry config class/template. A custom class loader loads the modules once at startup (it's not actually dynamic).
If I correctly understood what you meant, Tapestry-IoC already does that automatically: http://tapestry.apache.org/tapestry5.1/tapestry-ioc/autoload.html
a) locating pages stored in different packages
Tapestry already does that: http://tapestry.apache.org/tapestry5.1/cookbook/lib.html
b) obtain an instance of the page, initialize it and use it?
Take a look at ComponentSource.getPage(); -- Thiago H. de Paula Figueiredo Independent Java consultant, developer, and instructor http://www.arsmachina.com.br/thiago --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
