Closed bertfrees closed 6 years ago
I think this is a problem inherent to all OSGi services that are used in non-OSGi aware contexts.
We could either dynamically update the configurations, but I'm not sure if that would match peoples expectations. Or we could invalidate the configurations, i.e. make it throw errors, but that might even be worse that the current solution.
The same problem exists when extension functions and extension steps are unloaded.
we don't need much dynamicity
I would even dare to say we don't need it at all.
Depends on: