Re: [Exist-open] rev.12055 ability to override configuration attribute values specified in conf.xml

[Dmitriy S. <sha...@gm...>]

Hi all,

The
http://exist.svn.sourceforge.net/viewvc/exist/branches/shabanovd/animo/
have new configuration mechanism & it going to be used by new security
module.

The idea quite simple

@ConfigurationClass("database")
public class BrokerPool extends Observable implements Database {
...
	@ConfigurationField("min")
	private int minBrokers = 1;

linked with xml structure
<database min="1"> ...

Some time, minBrokers have default setting 1.

More on a way ...

-- 
Cheers,

Dmitriy Shabanov

On Tue, 2010-07-27 at 09:13 +0100, Thomas White wrote:
> Dannes ,
>  
> The idea is to separate the default setting that come with eXist
> distribution form the particular custom local settings that a specific
> installation or a box has.  
>  
> Use cases:
> 1. I have a some specific config settings for an application used:
>       a) on my developer's box; 
>       b) for client A for application ZZ on box VVV
>       c) for client A for application ZZ on box YYY
>       d) for client B, all the way to client Q ... all possible
> variations agian
>  
> If I want to check out a new version of eXist and run a clean build in
> place, I need to open each and every conf.xml and make the changes
> manually. And this goes for all other configuration files as well.
>  
> With few installations it is not an a serious issue. But is not very
> practical if one has many config variations on many client sites. 
>  
> Separating the custom from the system settings is a very common
> practice when deploy applications on clients machines. Otherwise all
> custom settings will be lost. Actually this is what happens now when
> we install a new eXist build.
>  
> If we can overwrite the config settings with command line parameters
> (which is very cool), what is the difference (or the problem) to have
> the custom settings grouped in a file? It is controlled, predictable
> and stable to use XML files to hold parameters. :-)
>  
> Could you please elaborate on why it is not a good idea to have an
> option to overwrite system settings from a file? 
> To me, to reduce the manual work and reuse/change settings easily as a
> very good idea.
>  
> Thomas
>  
> 
> ------
> 
> Thomas White
> 
> Mobile:+44 7711 922 966
> Skype: thomaswhite
> gTalk: thomas.0007
> Linked-In:http://www.linkedin.com/in/thomaswhite0007
> facebook: http://www.facebook.com/thomas.0007
> 
> 
> 
> 
> On 27 July 2010 08:31, Dannes Wessels <da...@ex...> wrote:
>         Hi,
>         
>         On Tue, Jul 27, 2010 at 8:49 AM, Thomas White
>         <tho...@gm...> wrote:
>         > Just a thought. What about if we can specify an XML file
>         with the
>         > parammeters we want to overwrite.
>         
>         
>         Hmmm so basically we have this XML document conf.xml ......
>         from which
>         settings now can be overwritten using a system properties
>         [maybe a bad
>         idea anyway, there are rough ideas to change the configuration
>         anyway], and now... you suggest to introduce another XML
>         document to
>         overwrite the defaults?
>         
>         Probably we do not want to do that..........
>         
>         D.
>         
>         
>         
>         --
>         eXist-db Native XML Database - http://exist-db.org
>         Join us on linked-in: http://www.linkedin.com/groups?gid=35624
> 
> ------------------------------------------------------------------------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share 
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://ad.doubleclick.net/clk;226879339;13503038;l?
> http://clk.atdmt.com/CRS/go/247765532/direct/01/
> _______________________________________________ Exist-open mailing list Exi...@li... https://lists.sourceforge.net/lists/listinfo/exist-open
-- 
Cheers,

Dmitriy Shabanov