Hi everyone,
I'm using felix configuration admin implementation since long time now and
it's works great, but I've got some big problems with the OSGI
configuration admin specification :
When a update() is called on a configuration, the configuration admin
service, first, will store the configuration and after, will schedule the
call of the updated function on the ManagedService
My problems are here :
-If during the execution of ManagedService.updated(), the new
configuration can't be applied, the only way to restore previous
configuration that I've found is to recall update function on the
configuration with previous dictionnary.
But this solution need my ManagedService to have a dependance with the
configuration admin service and so break the white board pattern,
furthermore, even if I raise a ConfigurationException, a
ConfigurationEvent.CM_UPDATED is fired and can create some bugs in my
application.
-My second problem is when a suthdown or a crash occurs after the
configuration is save but before that the ManagedService.updated()
function was called, if the configuration was good, no problems, but if
the new configuration has problems, I can't restore the previous
configuration after my application restart.
The solution that I've found is to add a function in my PersistanceManager
to really store the configuration on disk, and I call this function when
the ManagedService.updated() function succesfully execute. But to do this
I need a dependance with my persistanceManager and it's not really clean.
Now I thinks to create my custom configuration admin implementation but
before, do you know standards solutions for these problems ? I've search
in the OSGI specifications but I've don't find anythink.
Regards,
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
