[prev in list] [next in list] [prev in thread] [next in thread] 

List:       esb-java-dev
Subject:    [Carbon-dev] Handling Configuration files in components
From:       Srinath Perera <srinath () wso2 ! com>
Date:       2011-03-31 7:47:00
Message-ID: AANLkTingu5JLgm-Ntr9e4N9RfM3CRqER935v9vX=qQ7u () mail ! gmail ! com
[Download RAW message or body]

Hi All,

Each component should be able to work by just adding  component to the
carbon server without any configurations.

One common problem when trying to achieve this is  configuration
files. If the component depends on the configuration files, it might
fail to start.

I chatted about this with Azeez, and following is what we think is the
right procedure.

1. Each component should check CARBON_HOME/conf/advanced for the
configuration file (if there is any)
2. If file is found, start the component using the configuration file
3. Each component should have a default configuration file within the
jar, and if configuration file not found in the
CARBON_HOME/conf/advanced, boot the compoant using the default
configuration file.

If #3 is not possible, it should be discussed in this list, and we can
find a solution collectively.

--Srinath






-- 
============================
Srinath Perera, Ph.D.
  Senior Software Architect, WSO2 Inc.
  Visiting Faculty, University of Moratuwa
  Member, Apache Software Foundation
  Research Scientist, Lanka Software Foundation
  Blog: http://srinathsview.blogspot.com/
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[prev in list] [next in list] [prev in thread] [next in thread]