On Thu, 06 Jan 2011 13:07:34 -0200, Joel Halbert <j...@su3analytics.com>
wrote:
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?
One JAR can have as many modules as you want, so you don't need one JAR
per service. And Tapestry-IoC doesn't offer any way of selectively enable
or disable services provided by a module. IMHO I don't miss this feature
at all.
Searching the mailing list archives I've found this thread with a solution
for disabling the autoloading of given modules:
http://tapestry.1045711.n5.nabble.com/T5-disable-loading-specified-module-td2431110.html
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
