Re: [Hawkular-dev] About configuration

If the main hawkular deliverable is an integrated solution that builds on wildfly, then the priorities are clear and the configuration question is already answered. It doesn’t matter what configuration option you provide for the components themselves, because once integrated the configuration becomes subject of the target environment. Whatever mechanism you chose, it’s very likely going to be replaced by the mechanism the target environment uses. Therefore I would suggest the following: a) every component provides configuration builder interface (java, programmatically) b) the main configuration use the default wildfly mechanism a) allows the community to build custom adapters if needed. b) interfaces with a) and covers the main hawkular use cases. /HeikoB