Re: [java] config file defaults (was Re: Testing Java Broker & Client)
I was just wondering why using the config.xml is causing problems for people ? Or do you mean running a broker instance in your IDE perhaps ? Thanks, Marnie On 2/2/07, Robert Greig <[EMAIL PROTECTED]> wrote: On 02/02/07, Kevin Smith <[EMAIL PROTECTED]> wrote: > Speaking from a testing perspective - this would be very useful. One of the > difficulties I'm encountering testing my code changes is figuring out how to get > a sanely configured broker instance up and running. Did you not start with the default config.xml file located in the etc directory? RG
Re: [java] config file defaults (was Re: Testing Java Broker & Client)
On 02/02/07, Kevin Smith <[EMAIL PROTECTED]> wrote: Speaking from a testing perspective - this would be very useful. One of the difficulties I'm encountering testing my code changes is figuring out how to get a sanely configured broker instance up and running. Did you not start with the default config.xml file located in the etc directory? RG
Re: [java] config file defaults (was Re: Testing Java Broker & Client)
On 02/02/07, Gordon Sim <[EMAIL PROTECTED]> wrote: Robert Godfrey wrote: > Yes - you'll definitely need the cofig that;s already in the config.xml... > you just want to add your stuff extra. Though a minor issue at this point, it would be nice if there were defaults for all config items such that even without a config file (or a 'complete' one) you could run the broker. For items that use the attributes we wrote do make configuration simpler, defaults can be specified as part of the attribute (in code). I think it's for the more dynamic bits that we don't currently have default (e.g. the entire section on the principal-databases for example). RG
Re: [java] config file defaults (was Re: Testing Java Broker & Client)
Gordon Sim wrote: Robert Godfrey wrote: Yes - you'll definitely need the cofig that;s already in the config.xml... you just want to add your stuff extra. Though a minor issue at this point, it would be nice if there were defaults for all config items such that even without a config file (or a 'complete' one) you could run the broker. Clearly that might mean e.g. that authentication was restricted to guest/guest if no password file, memory store and default mina chain was used etc. It would make it a bit easier to get up and running though. Speaking from a testing perspective - this would be very useful. One of the difficulties I'm encountering testing my code changes is figuring out how to get a sanely configured broker instance up and running. I'm not a big fan of hardcoding defaults but maybe embedding a minimal config file in the broker jar would work. We could check for it if no config is specified on the command line. --Kevin
