> why cant you take the jar from the classpath? This is what I have done, but it strikes me as quite a blunt instrument to use for configuring an application. Does it really mean you need a jar per service, if the user of the jar might want to selectively enable some of the services but not others?
On Thu, 2011-01-06 at 06:56 -0800, Josh Canfield wrote: > That quote doesn't help because its in the manifest of the jar you want to > exclude... why cant you take the jar from the classpath? > On Jan 6, 2011 6:53 AM, "Josh Canfield" <joshcanfi...@gmail.com> wrote: > > 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 > >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
