On Fri, 03 Feb 2012 14:24:35 -0200, Erik Fäßler
<erik.faess...@uni-jena.de> wrote:
I thought of the component to become a IoC module. But I fear, modules
are kind of static, too - I can't have different "instances" of a
module, can I?Point is, all configuration parameters defined in a module
are global as far as I know. This would be just like the static
configuration class I have problems with.
Not of the same module, but you can always have multiple services wrapping
around some data (in this case, configuration) and have this services
allow changing the configuration on the fly.
Is there a convenient way to deal with such situations? Or am I just
failing the design goal of Tapestry's IoC container here? I would like
to use the IoC container to manage the parts of my component and would
regret when this would not be possible due to my multiple-deployment
requirement.
Don't forget you can have different JARs with different module classes
providing different implementations for the same service interface. This
is not a problem at all. You can even define a given module will be loader
or not through system properties. Check the documentation.
--
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
