On 10/09/2007, at 1:10 PM, Joakim Erdfelt wrote:
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.
I'm confused, what is the ongoing source of the information (and what
is sourcing it) while the application is running?
Currently, the configuration components are what is used by
everything to determine the config, and that comes from in memory.
And I thought you only said the database was for reporting - which is
not implemented yet - and was the other part of this thread?
Sorry for all the dense questions :)
- Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
