> 1. config admin can be r no available Use system properties or default values at the start. We should do this regardless whether configuration is available or not.
> 2. config admin can start after our bundle When this is started, If there is configuration, #updated method will be invoked. Handle port changes if there is one. > 3. config admin can be stopped Use whatever latest configuration. All we have to care whether updated method is invoked. > 4. config admin can be restarted Do #2 > 5. config admin can be there but to not have a configuration for us See #1, as this is no different between config admin is not available. > 6. will be nice not to bind the connector based to the system properties and > configuration admin to be started after our bundle and rebind I'm not sure what you meant by this. > ... > If we stick to if confing admin not present bind based on sys props then is > simple. Question sis: do we? This is a valid question. I would prefer if http service can be configured via config admin. Regards, Edward Yakop _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
