Hi -- For most things, I agree that the java-based configuration approach is best. For us the exception is that we DO want some stuff exposed in a way that does not involve editing java code. Changing java code requires a full build/test/verification process, which should not be necessary for something like configuration changes.
Sysadmins / product managers should be able to change configurations without needing an IDE or a java developer. ( output directories, which background tasks are enabled ) Everything else... absolutely hands-off! While chenille-hivemind is a good intermediate step, we obviously would like a pure T5 solution at some point. P.S. before someone suggests system properties... No! system properties are only used for temporary changes not permanent decisions. ( + does not work for random multi-line text ) On Wed, Sep 30, 2009 at 4:00 PM, Kalle Korhonen <kalle.o.korho...@gmail.com>wrote: > Yes, Hivemind had great concepts but tapestry-ioc provides all of the > same in a much simplified package (building pipelines comes to mind as > one of the good examples). But this integration offers a very nice way > to transition at your own pace. > > Kalle > >
