Wendy Smoak wrote: > On 9/9/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote: > > >> The database was always viewed as *the* source for all information that >> is pertinent to Archiva. >> The configuration pieces were viewed not as a model or datasource, but a >> bootstrap to take a configuration from disk, and populate the database. >> > > ... viewed that way by whom? Not me! I consider archiva.xml *the* > source for configuration. > > I need to be able to pre-configure _everything_ in plain text, so at a > minimum it needs to keep dumping the information to archiva.xml on > shutdown and reading it back in on startup. > >
I think you misunderstand what I said. Ideally, the information in the DB is what is used at runtime. And the information provided by the configuration components is just used to bootstrap / startup the app, not as an ongoing source for the information while the application is running. The filesystem based configuration is in no danger of going away or being replaced, it is too important for those kinds of sinful thoughts. - Joakim
