Frank Hölting wrote
> Hi,
> 
> i suspect that the 1... n possible PersitenceManager is an unused option. 
> There would have to be several configuration sources for this, e. g. DB, File 
> or SCM. In my opinion, there should be only one PersistenceManager service 
> registration at runtime.

Yes, I forgot to mention this in the issue. It might be sufficient to
just support a single PM.

> 
> However, since I cannot speak for everyone, the proposal is acceptable.  
> 
> The list is then passed by e.g. -Dfelix.pm=a,b of the Configuration Admin 
> implementation? I wonder how the Configuration Admin reacts to the service 
> registration sequence. 
> 
> Example:
> -Dfelix.pm=a,b
> Case 1: The service registration has the sequence "b", "a" 
> Case 2: Only "b" is registered.
> 
> In case 1: Does the CA implementation wait until PersistenceManager "a" is 
> registered?

Yes.
> In case 2. Will it wait forever or will a timeout be implemented?

It will wait forever as the requirements are not satisfied.

> 
> If I'm not mistaken, the current implementation can only use one 
> PersistenceManager for the active saving of the component configuration.  The 
> PersistenceManager with the highest service ranging is allowed to store.
> If PersistenceManager "a" is not available, will "b" be saved? Is "a" then 
> present again, then the wrong configuration is provided? Multiple dynamic 
> configuration sources are not easy to manage.  

Totally agree with that. So maybe we just go with a single PM. It's
easier to handle, easier to understand and easier to implement.

Thanks
Carsten

> 
> For my specific case -Dfelix. pm=a is fine. 
> 

 

-- 
Carsten Ziegeler
Adobe Research Switzerland
[email protected]

Reply via email to