I was hoping that I can get around without modifying additional files. On the other hand having a declaration makes sence because the container
needs to know about components in order to do its work. The idea is that
we have a large application for which we have a large number of service. Most of them won't be configurable from avalon xconf file. It would be interesting to be able to have two configuration files, one maintaned manually and the other automatically.
Regards, Peter.
J Aaron Farr wrote:
--- Peter Severin <[EMAIL PROTECTED]> wrote:
Most of our components won't need a special configuration so I don't implement the Configurable interface and don't put any configuration inside the xconf file. I would be very unpleasant to have to manage another file besides with roles.
AFAIK, if you want to use a component you must have an entry in the xconf file. This does not mean it has to contain configuration data. In other words, think of the xconf file as a declaration on which components are to be used in your application.
<my-xconf> <comp1 id="no-config"/> <!-- notice no configuration --> <comp2 id="config"> <data> value </data> </comp2> </my-xconf>
If you want to only manage a single file, it should be the xconf file. With the newer meta-format declaration of roles, you don't have to have a roles file.
jaaron
__________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
