>From the link; "Module autoloading isn't 100% free ... you must tell Tapestry IoC where the modules to load are located, which can be done via a Manifest file entry, or via an annotation."
I don't believe being in the classpath is enough. I'm not sure there is a way to prevent a dependent module from loading. On Jan 6, 2011 3:54 AM, "Joel Halbert" <j...@su3analytics.com> wrote: > As I understand it Tapestry-IOC will autoload any modules that it finds. > > http://tapestry.apache.org/autoloading-modules.html > > > Is there a way to explicitly disable the loading of certain modules, > other than removing the jar in which the module is packaged from the > classpath? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org >
