Change in bundle deploy behaviour

[thomas.diesler]

In AS7-4840 Rico says

OK, understood - even if I find this disturbing as a change in behavior between 7.1.1 and 7.1.2.

But how is one supposed to configure the start of OSGi bundles after deployment? Not using the CLI/Console of course, but to configure it to call the activator on each start-up?

The reasoning is that that we don't want to create an implicit ordering requirement on the 'deploy' operation. IOW it should be possible to deploy artefacts in any order. I suspect that future AS7 versions will have a --start flag on the deploy operation. In that respect the AS behaves like any other OSGi runtime. You first install all the bundles you need (in any order), then you start possible a subset of installed bundles.

On restart, the framework is expected to automatically start bundles according to their respective persistent state. In AS7, the expected behaviour is that bundles which were active on shutdown also become active automatically on server restart.

I agree that autostart for simple deployment scenarios (i.e. one bundle with no dependencies) is very convenient. Perhaps you can think of a process that that works for both - the simple and complex use case.

[mreasy]

Thanks Thomas, for summing it up.

I would be OK with the complex use case, but how can I configure bundles to get started (IOW: mark them active)?

[thomas.diesler]

You start them via the CLI, Console, JMX integration or some other management api/tool that supports Bundle.start()

If you look at the felix webconsole it works very similar, only that we haven't (yet) a flag for "start on deploy". In AS7.1.2 its a second discrete step.

[bosschaert]

FYI here's some documentation and some examples on how to start the bundles from the CLI: http://docs.jboss.org/author/display/JBOSGI/Command+Line+Interface+Console

The web console is documented here: http://docs.jboss.org/author/display/JBOSGI/Management+Console