Em Tue, 15 Dec 2009 06:10:30 -0200, Peter Rietzler
<[email protected]> escreveu:
Hi
Hi!
We are heavily using Tapestry IOC to structure our application into
modules.
When we create a concrete instance of our application we decide which
modules should be part of it by just setting the appropriate modules in a
@SubModule annotation.
Why don't you use module autoloading for that? Just drop the JAR
containing the module in the classpath and everything works. No need to
use @Submodule for that.
Is there a way to define a contribution as optional ?
Now, there isn't. You can file a JIRA for it. I guess it will be easy to
implement.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
