On Mar 13, 2007, at 10:29 AM, Pablo Oliveira wrote:

> On Mar 13, Vincent Massol wrote :
>> We'll have to take a decision here in the future:
>> 1) either we provide a configuration per component
>> 2) or we provide a global configuration
>>
>> I prefer 1) because:
>> - a component is encapsulated completely in a JAR
>> - a component shouldn't  see by default configuration from other
>> components. It's these other components who should offer APIs to
>> return configuration data if required
>
> I also like 1 better.
>
> Yet I think from a user point of view, it seems more natural to edit a
> single xwiki.cfg file than to edit a conf file inside some component's
> JAR meta data. So I would still allow some global way of overriding
> components configuration from a single configuration source.

Yes you're right...

There are 2 different types of configurations:
- static ones
- dynamic ones that can be modified by the user

So component should have a default configuration so that they should
work out of the box but users should be allowed to modify the
configuration through an interface (in the wiki itself for example as
it's currently done maybe).

I'm not entirely sure about all this yet. Need to think more about it.

Thanks
-Vincent