>Now Jörg suggested the context-aware configuration override mechanism >[2] >which makes sense except that all relevant configuration parts >like distribution/replication agents, externaliser and other OSGi >configurations (e.g. for jdbc db configs or search engine end points) >are not configured via caconfig today.
and caconfig was never intended as a replacement for system configuration, but only as an addition for context-aware configuration which cannot be managed elegantly as OSGi configurations. most sensitive configurations like jdbc configs etc. are system configurations and in most cases not context-aware. stefan
