[server] Splitting configurations /configuration cleanup

[Norman Maurer <no...@apache.org>]

Hi all,

I would like to split the current configuration file
(james-config.xml) of james in a more logical way. I think keeping
everything in one file is just confusing. I would like to split the
config file to one file per service/component. I think this would make
it even easier for us to reload config per service etc later.

This would give us something like:


pop3server.xml
imapserver.xml
smtpserver.xml
remotemanager.xml
james.xml
spoolmanager.xml
dnsserver.xml
domainlist.xml
management.xml
mailstore.xml
users-store.xml
virtualusertable-store.xml
spoolrepository.xml

(maybe using one config for all the stores + repostory).

I would also like to remove all the commented mailets and just keep
the "important" ones. If users / devs really want to add an extra
mailet then they should read up on them on the docs.

WDYT ?

Bye,
Norman

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

Re: [server] Splitting configurations /configuration cleanup

[Norman Maurer <no...@googlemail.com>]

Hi Eric,

to be honest you will not be able to reuse your config.xml without
modifications. Current development version of james is not compatible
(config-wise) with 2.3.x. We will provide "migration" informations to
our users once the new configuration layout is worked out.

Bye,
Norman

Ps: I think we can stilll provide a config.xml file which includes all
other xmls.

2010/1/27 Eric MacAdie <er...@macadie.net>:
> It would be nice to be able to use my current config.xml in future versions
> of James. I have been thinking about making a Swing app for editing the
> James config file.
>
> Regards,
> Eric MacAdie
> Pronounced: muh-KAY-dee
>
> Norman Maurer wrote:
>>
>> Hi all,
>>
>> I would like to split the current configuration file
>> (james-config.xml) of james in a more logical way. I think keeping
>> everything in one file is just confusing. I would like to split the
>> config file to one file per service/component. I think this would make
>> it even easier for us to reload config per service etc later.
>>
>> This would give us something like:
>>
>>
>> pop3server.xml
>> imapserver.xml
>> smtpserver.xml
>> remotemanager.xml
>> james.xml
>> spoolmanager.xml
>> dnsserver.xml
>> domainlist.xml
>> management.xml
>> mailstore.xml
>> users-store.xml
>> virtualusertable-store.xml
>> spoolrepository.xml
>>
>> (maybe using one config for all the stores + repostory).
>>
>> I would also like to remove all the commented mailets and just keep
>> the "important" ones. If users / devs really want to add an extra
>> mailet then they should read up on them on the docs.
>>
>> WDYT ?
>>
>> Bye,
>> Norman
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

AW: [server] Splitting configurations /configuration cleanup

[Mario Zsilak <ma...@inew-cs.com>]

Hi,

Splitting up the stuff is IMO a good idea, because the current config-file
is way too big. However I would keep the commented stuff, because it helps
new users a lot in getting into james and to show what is possible. 

At least it helped me a lot :)

Kind regards,
Mario

-----Ursprüngliche Nachricht-----
Von: Eric MacAdie [mailto:eric@MacAdie.net] 
Gesendet: Mittwoch, 27. Jänner 2010 21:08
An: James Developers List
Betreff: Re: [server] Splitting configurations /configuration cleanup

It would be nice to be able to use my current config.xml in future 
versions of James. I have been thinking about making a Swing app for 
editing the James config file.

Regards,
Eric MacAdie
Pronounced: muh-KAY-dee

Norman Maurer wrote:
> Hi all,
>
> I would like to split the current configuration file
> (james-config.xml) of james in a more logical way. I think keeping
> everything in one file is just confusing. I would like to split the
> config file to one file per service/component. I think this would make
> it even easier for us to reload config per service etc later.
>
> This would give us something like:
>
>
> pop3server.xml
> imapserver.xml
> smtpserver.xml
> remotemanager.xml
> james.xml
> spoolmanager.xml
> dnsserver.xml
> domainlist.xml
> management.xml
> mailstore.xml
> users-store.xml
> virtualusertable-store.xml
> spoolrepository.xml
>
> (maybe using one config for all the stores + repostory).
>
> I would also like to remove all the commented mailets and just keep
> the "important" ones. If users / devs really want to add an extra
> mailet then they should read up on them on the docs.
>
> WDYT ?
>
> Bye,
> Norman
>
>
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

Re: [server] Splitting configurations /configuration cleanup

[Eric MacAdie <er...@MacAdie.net>]

It would be nice to be able to use my current config.xml in future 
versions of James. I have been thinking about making a Swing app for 
editing the James config file.

Regards,
Eric MacAdie
Pronounced: muh-KAY-dee

Norman Maurer wrote:
> Hi all,
>
> I would like to split the current configuration file
> (james-config.xml) of james in a more logical way. I think keeping
> everything in one file is just confusing. I would like to split the
> config file to one file per service/component. I think this would make
> it even easier for us to reload config per service etc later.
>
> This would give us something like:
>
>
> pop3server.xml
> imapserver.xml
> smtpserver.xml
> remotemanager.xml
> james.xml
> spoolmanager.xml
> dnsserver.xml
> domainlist.xml
> management.xml
> mailstore.xml
> users-store.xml
> virtualusertable-store.xml
> spoolrepository.xml
>
> (maybe using one config for all the stores + repostory).
>
> I would also like to remove all the commented mailets and just keep
> the "important" ones. If users / devs really want to add an extra
> mailet then they should read up on them on the docs.
>
> WDYT ?
>
> Bye,
> Norman
>
>
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

Re: [server] Splitting configurations /configuration cleanup

[Manuel Carrasco Moñino <ma...@apache.org>]

+1

On Sat, Jan 30, 2010 at 1:28 PM, Mario Zsilak <ma...@inew-cs.com> wrote:
>
>
>>> I would also like to remove all the commented mailets and just keep
>>> the "important" ones. If users / devs really want to add an extra
>>> mailet then they should read up on them on the docs.
>>
>> This will end up in spoolmanager.xml .. maybe we could have a
>> spoolmanager.xml.example with the commented stuff?
>>
>> Stefano
>
>
> +1
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

AW: [server] Splitting configurations /configuration cleanup

[Mario Zsilak <ma...@inew-cs.com>]

>> I would also like to remove all the commented mailets and just keep
>> the "important" ones. If users / devs really want to add an extra
>> mailet then they should read up on them on the docs.
>
> This will end up in spoolmanager.xml .. maybe we could have a
> spoolmanager.xml.example with the commented stuff?
> 
> Stefano


+1

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

Re: [server] Splitting configurations /configuration cleanup

[Stefano Bagnara <ap...@bago.org>]

2010/1/27 Norman Maurer <no...@apache.org>:
> Hi all,
>
> I would like to split the current configuration file
> (james-config.xml) of james in a more logical way. I think keeping
> everything in one file is just confusing. I would like to split the
> config file to one file per service/component. I think this would make
> it even easier for us to reload config per service etc later.

I'm fine with this change. Ideally I'd like to extract some basic
variable to a property file, so that hostname, servernames, dns
servers and other *MUST CHANGE* configuration are in the property
files so that for a basic setup you don't have to touch the xml (maybe
spring can help us here?)

> This would give us something like:
>
>
> pop3server.xml
> imapserver.xml
> smtpserver.xml
> remotemanager.xml
> james.xml
> spoolmanager.xml
> dnsserver.xml
> domainlist.xml
> management.xml
> mailstore.xml
> users-store.xml
> virtualusertable-store.xml
> spoolrepository.xml
>
> (maybe using one config for all the stores + repostory).

+1

> I would also like to remove all the commented mailets and just keep
> the "important" ones. If users / devs really want to add an extra
> mailet then they should read up on them on the docs.

This will end up in spoolmanager.xml .. maybe we could have a
spoolmanager.xml.example with the commented stuff?

Stefano

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org