Re: ConfigurationAdmin -> move default FilePersistenceManager to own bundle

2017-08-26 Thread Carsten Ziegeler
Thanks for your mail. As you note, such a change would break all other users (or at least all users not using the default persistence manager). Therefore moving it to another bundle is maybe a too dramatical change. Now, what about a simpler solution: adding the evaluation of a framework property.

ConfigurationAdmin -> move default FilePersistenceManager to own bundle

2017-08-26 Thread mailing-list
By write and use a implementation of my own PersistenceManager the default FilePersistenceManager start with the cm bundle and after this default implementation, my own implementation with a higher service id. But my implementation not use and the default implementation calls the ManagedService