7 Replies Latest reply on Dec 10, 2012 3:36 AM by thomas.diesler

How to undeploy osgi bundle

graben Dec 5, 2012 11:33 AM

If I deploy osgi bundle via adding a new capability via cli the artefact is automatically deployed and started, but if do a remove capability the config is changed as expected but the package is still deployed and running in the runtime environment. I this solveable via cli or dmr?

Best,

Benjamin

1. Re: How to undeploy osgi bundle

thomas.diesler Dec 7, 2012 4:02 AM (in response to graben)

This is a bug. Change in osgi subsystem configuration should not take effect until server/subsystem restart.
1 of 1 people found this helpful
Actions
2. Re: How to undeploy osgi bundle

graben Dec 7, 2012 5:55 AM (in response to thomas.diesler)

Hi Thomas,

which part is the bug the deployment or the undeployment?

Did you create an issue?

Best,
Benjamin
Actions
3. Re: How to undeploy osgi bundle

thomas.diesler Dec 7, 2012 7:09 AM (in response to graben)

Related issues are referenced at the top right.
Actions
4. Re: How to undeploy osgi bundle

graben Dec 7, 2012 9:00 AM (in response to thomas.diesler)

Sorry, I didn't saw it. :-)
Actions
5. Re: How to undeploy osgi bundle

thomas.diesler Dec 7, 2012 10:52 AM (in response to graben)

UR welcome - glad to have you here.
Actions
6. Re: How to undeploy osgi bundle

graben Dec 9, 2012 10:34 AM (in response to thomas.diesler)

Just finalize. What's the reason for un subsystem restart if adding new capability, and how can I do this programatically without restarting the hole server.

THX Benjamin
Actions
7. Re: How to undeploy osgi bundle

thomas.diesler Dec 10, 2012 3:36 AM (in response to graben)

Capabilities added to the server configuration are (as the name suggests) part of the server configuration. Like many other configuration items, they cannot be changed at runtime. OSGi subsystem capabilities specifically are processed at bootstrap time in a known order. This is done before any persistent user bundle gets deployed. It is therefore guranteed that user bundles can see capabilities exposed by the subsystem configuration.

Part of the contract for changing system configuation is that you transitively restart the subsystems that may be effected by the configuration change. In many cases, the transistive graph of effected subsystems is not known - so a server restart is the only sensible option.
Actions

Go to original post