Sounds good. I think that the component could check for a "components.properties" in the classpath and use it to load default properties. However, properties should be prefixed by the component name: servicemix-http.connectorMaxIdleTime = 60000 These properties should be overriden by the usual property file which can be update dynamically using jmx.
Another way would be to use JNDI to retrieve the values, but I think the "components.properties" is an easier way to go. On 10/17/06, Thomas TERMIN <[EMAIL PROTECTED]> wrote:
Hello Guillaume, it would be good if the component.properties file could be also available in servicemix_home/conf. I would change the MBean so that if no component.properties file is available in workspace then the MBean searches for occurrences in the conf directory. The problem is that we copy the file in the workspace directory before the servicemix is started the first time. But if you then start servicemix the complete directory structure will be newly created. What do you think? Cheers, Thomas Termin
-- Cheers, Guillaume Nodet
