Pete: > Once the Keel Server (aka Avalon container) has started up, is all > configuration via the system.xconf files done?
Via the files, yes, but that's not necessarily the only way to do configuration. > In other words, system.xconf files are only for that portion of the > configuration data which does not change after the avalon container > starts up.... Again, normally yes... > The reason I am asking is that > component A does it's job, which is to configure component B's startup > parameters. > Then component B starts up. As a "Configuration" is an interface, it's possible to instantiate one dynamically (e.g. from component A) and have B passed this configuration object, rather than reading it through the usual channels. We use this trick in a few places. Technically, component B is *not* "Configurable", but it has a configure(Configuration) method anyway, which is called by A - particularly if A is a kind of factory, such as PersistentFactory (which uses this technique). > And of course the system.xconf xml would be a perfect medium to write > component B's startup configuration. > > But I assume that any configuration going to the second component has to > go via some other medium than the system.xconf file, even if that > particular component has not started up yet. Is that assumption correct? Yes, it is, AFAIK Mike JGlobal Ltd. http://www.jglobal.com http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
