Hello all,
I'm still planning to reformulate an existing component, which has grown quite
large, into Tapestry IoC (no webapp). One reason for the re-writing of this
component is the following problem:
The component features a static configuration class which is initialized once
at startup. Then, all other parts of the component can get configuration values
from this class.
The problem arises when I want to run multiple instances of the component which
are configured differently; Since the configuration class (and attributes) is
static, I can only hold one configuration parameter set available at a given
time within a JVM. But I need the possibility to have multiple "instances" of
my component, each of which does a different job. I want to solve multiple
related tasks, all of which can be done by this single component - however with
different parameters.
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.
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.
I hope I made my thoughts clear and someone can give me a good hint.
Best regards,
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
