Am 14.12.2016 um 15:38 schrieb Carsten Ziegeler 
<cziege...@apache.org<mailto:cziege...@apache.org>>:

Felix Meschberger wrote
Hi

I think this is a good topic to discuss on a broader level.

I once implemented a function with two services configured through OSGi 
Configuration being able to overwritten by framework properties (aka system 
properties). What I did implement is a helper function which first checked the 
system property and if not set would revert to the OSGi configuration and if 
that was also not set revert to a default value.

I wonder, whether we could not make function available on a broader bases, such 
as through the OSGi Configuration Admin Service ?

Of course this has consequences when we start thinking in terms of „and what if 
I update configuration ?“ I think this goes into the discussion of immutable 
systems.

I guess this can be done with a ConfigurationPlugin transparently

Ah ! Nice catch. And with the updated ConfigurationAdmin specification we can 
be reasonably sure this to be applied to DS configurations as well. Right ?

… and now for some side track coding of this ;-)

Thanks
Felix



Carsten

(Yes I know this is not standard, but lets start thinking about it and we might 
make it a standard…)

Regards
Felix

Am 14.12.2016 um 14:40 schrieb Bertrand Delacretaz 
<bdelacre...@apache.org<mailto:bdelacre...@apache.org>>:

On Wed, Dec 14, 2016 at 12:07 PM, Robert Munteanu 
<romb...@apache.org<mailto:romb...@apache.org>> wrote:
...The idea is to allow the user to redefine it at runtime via system
properties:

java -jar ... -Dmpx.repository.home=/some/place ...

FWIW the crankstart launcher supports this, I've just added an example
at http://svn.apache.org/r1774245 as that was not tested for configs
so far.

I think it's required for modern operations, where some things are
known only at runtime.

-Bertrand





--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org<mailto:cziege...@apache.org>

Reply via email to