13 Mar
2007
13 Mar
'07
10:08 a.m.
On Mar 13, 2007, at 10:02 AM, Pablo Oliveira wrote:
On Mar 13, Sergiu Dumitriu (JIRA) 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
-Vincent
P.S.: It's so bad that there's no better
way of getting
configuration parameters. There should be a separate component,
accessible from anywhere.
I really do agree here. This would be a great step towards a more
modular XWiki. Even if not related: It's really annoying to have
to pass an XWiki instance to the storage module, just so it can
retrieve some conf parameters... 
13 Mar
13 Mar
10:29 a.m.
New subject: [xwiki-dev] Re: [xwiki-commits] [Issue] Commented: (XWIKI-942) Customize default cache duration
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.
Pablo
10:37 a.m.
New subject: [xwiki-dev] Re: [xwiki-commits] [Issue] Commented: (XWIKI-942) Customize default cache duration
On 3/13/07, Pablo Oliveira <pablo.oliveira(a)enst.fr> wrote:
On Mar 13, Vincent Massol wrote :
I also think that we need both.
--
http://purl.org/net/sergiu
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.
Pablo 
10:46 a.m.
New subject: [xwiki-dev] Re: [xwiki-commits] [Issue] Commented: (XWIKI-942) Customize default cache duration
We can use both . if can it is better for us
Regards
-Phung Nam
On 3/13/07, Sergiu Dumitriu <sergiu.dumitriu(a)gmail.com> wrote:
On 3/13/07, Pablo Oliveira <pablo.oliveira(a)enst.fr> wrote:
On Mar 13, Vincent Massol wrote :
I also think that we need both.
--
http://purl.org/net/sergiu
--
You receive this message as a subscriber of the xwiki-dev(a)objectweb.orgmailing list.
To unsubscribe: mailto:xwiki-dev-unsubscribe@objectweb.org
For general help: mailto:sympa@objectweb.org?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
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.
Pablo
10:40 a.m.
New subject: [xwiki-dev] Re: [xwiki-commits] [Issue] Commented: (XWIKI-942) Customize default cache duration
On Mar 13, 2007, at 10:29 AM, Pablo Oliveira wrote:
On Mar 13, Vincent Massol wrote :
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
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.
11:05 a.m.
New subject: [xwiki-dev] Re: [xwiki-commits] [Issue] Commented: (XWIKI-942) Customize default cache duration
On 3/13/07, Vincent Massol <vincent(a)massol.net> wrote:
On Mar 13, 2007, at 10:29 AM, Pablo Oliveira wrote:
Maybe http://jira.xwiki.org/jira/browse/XWIKI-648 helps?
--
http://purl.org/net/sergiu
On Mar 13, Vincent Massol wrote :
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 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.
6397
days inactive
6397
days old
5 comments
4 participants
participants (4)
-
Pablo Oliveira -
Phung Nam -
Sergiu Dumitriu -
Vincent Massol