Jens Offenbach wrote > Now, I am confused... But I am using 'configuration-policy="require"'. This > should force SCR to activate my component only when there is a valid > configuration. >
Your configuration is changed, config admin fires a configuration changed event, which in turn reactivates your component. It might be the same configuration, but as someone updated the config, config admin needs to send out the event. If you don't implement modified, your component is deactivated and then activated. Otherwise modified is called. As you have require as the configuration policy, the only way to avoid this is to make sure that the configuration is not updated in config admin. So this is not an SCR problem, everything behaves as expected. It looks rather like a provisioning problem to me. In general, OSGi is dynamic, so your component should behave properly and expect this "restarting" through a configuration change. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
