Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ConfigurationAdmin issues introduced by the new Karaf runtime #94

Closed
kaikreuzer opened this issue Jan 17, 2016 · 1 comment
Closed

ConfigurationAdmin issues introduced by the new Karaf runtime #94

kaikreuzer opened this issue Jan 17, 2016 · 1 comment

Comments

@kaikreuzer
Copy link
Member

This is similar to #85.
Nothing to blame Karaf/FelixCM for as it is very likely fulfilling all specs.
Nonetheless, we observe many effects where the new behaviour causes existing functionality to break and if we find a way to make it more compatibly, it would be very valuable.

Some issues to look at:

I am not sure whether this might also only be a combination of CM and DS - for DS, there is also a different behavior, since components require now an immediate="true" to be started.

@kaikreuzer
Copy link
Member Author

There does not seem to be any general issue - most observations were due to a different start behavior of DS components.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant