Ok, thanks for that hint. Regards, Laci
> Am 19.06.2014 um 20:44 schrieb Achim Nierbeck <[email protected]>: > > Don't do that, require bundle is the worst you can do. > If you use that you loose all the benefits of OSGi. > Stick to the standard import and export maybe a dynamic-import every now and > than. But never ever use require bundle. > > Regards, Achim > > sent from mobile device > > Am 19.06.2014 16:35 schrieb "Laci Gaspar" <[email protected]>: >> Ok, just to close this... it was a problem with our deployment server, so >> sorry for the disturbance. >> >> But anyhow I learned that the Import-Package / Export-Package elements are >> best left alone. What I needed was only the <Require-Bundle> configuration >> in our pom. >> >> Thanks and regards >> Laci >> >>> On 19.06.2014 11:07, Achim Nierbeck wrote: >>> In such cases it sometimes help to issue the refresh command. >>> If you update a bundle another bundle using it, like a central cxf or camel >>> bundle (in case of camel the camel-core) are still bound to the "old" >>> uninstalled bundle. In those cases it helps to refresh these bundles after >>> an update of the bundle containing either cxf or camel-routes. >>> In your case I'm not sure which bundle does actually stick to an old one >>> therefore do a general refresh, which does refresh all bundles (it actually >>> does a re-wiring of the bundles) >>> >>> regards, Achim
