This is an area where there was simplification from HiveMind to T5 IoC.
Basically, in the relatively rare case that a single service needs multiple configurations, there really is not an alternative to creating different services, each one managing a specific set of data, with a "master" service that depends on the data services to access the configuration data. This doesn't work too poorly in practice; for instance, this is how Infrastructure and InfrastructureOverrides works. There's often some value add to separating out the concerns (related to the contributed data), such as simplifying the testing of the master service, since it does less. On 3/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
In T5 ioc, what is the recommended way for having multiple configuration points for a service? Do you do something like set up a service that is internal specifically for accepting contributions and then inject that into the real service being configured? - dan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
