directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ayyagarikiran <>
Subject Re: [server.xml] Discussion
Date Wed, 03 Dec 2008 12:27:15 GMT
hi Emmanuel,

Emmanuel Lecharny wrote:
> ayyagarikiran wrote:
>> hi Emmanuel,
>> Emmanuel Lecharny wrote:
>>> - Modifications to come
>>> As we will have to review the replication system, which is not 
>>> documented atm, it's pretty clear that we will have to modify the 
>>> server.xml file to deal with replication. Hopefully, this is an 
>>> isolate part of the configuration, so I'm not too worried about that.
>>> MINA 2 migration will impact the file a lot. We have added numerous 
>>> parameters, and removed the Datagram & Socket beans, replaced by 
>>> direct configurations into the different servers, but it might not be 
>>> the perfect idea. Tjis has to be discussed.
>>> We also have to work on a failover mechanism, based on a journalized 
>>> system (probably), and it will need some configuration too.
>>> So far, this is what comes to my mind currently, but this might be 
>>> partial.
>> I think embedded jetty server may also need to be configured through 
>> server.xml, IMO it may look like the below mentioned
>>  <!-- by default the jetty server is not enabled-->
>>  <jettyServer enable="false">
>>    <confFilePath>path/to/conf/file</confFilePath>
>> </jettyServer>
> Right, I forgot to mention that. There is also something about Quartz 
> integration.
hmm, isn't this a mandatory service which should run? ( which uses the LDAP store to store
its job info )
> At some point, having a monolithic server.xml will be totally 
> unmanageable. May be we should think about a more versatile system, with 
> sub files ?

hmm, IMHO configuring a system with more than one file may cause frustration to the user.

Kiran Ayyagari

View raw message