PROPERTY_AUTO_START

[adrian.brock]

Further to the resolver discussion;

I've removed the use of PROPERTY_AUTO_START since this is already
available in the deployment layer as DeploymentUnit.getRequiredStage()
Any processing done in OSGi, should respect what other apis choose for this flag,
although AFAIK nobody else uses it?

As far as I understand it, the purpose is to not "start" (resolve) bundles
unless they are needed by classloading or something in persistent storage says
they should be started.

The setting of the RequiredStage is already done by the OSGiBundleStateDeployer
when the bundle is installed, but there is currently no persistent state, so there is a
TODO there.

I've still yet to understand what all this extra processing is actually doing.
From what I described on a different thread, this processing is also broken:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=160839
I don't mean the choice of wrapper versus extension which is just a choice
of elegance and maintainability.

NOTE: This is very different from the lazy start feature of OSGi
where we should leave the deployment in the CLASSLOADER/RESOLVED stage
until somebody loads a class. What is happening here is things are being moved
to the INSTALLED/ACTIVE stage out of the normal sequence.

[thomas.diesler]

External bundle provisioning systems have different requirements on bundle start behaviour.

Clients that require explicit control over bundle start

* osgi management (web) console
* osgi testsuite for embedded/remote frameworks

Clients that require implicit bundle start

* Hot deployment service that picks up bundles from the deploy folder

Recent changes broke AS integration to the effect that bundles did not get started on sever startup.

Related to http://www.jboss.org/index.html?module=bb&op=viewtopic&t=163633

Please verify that container integration related changes are valid.

cheer

[thomas.diesler]

There is also a test case for this, which should run in embedded and all supported target containers

https://jira.jboss.org/jira/browse/JBOSGI-99

[adrian.brock]

I'll repeat. This should be a feature at the deployer's level.
If it is not implemented properly, then you should fix it there.

1) You can't expect other parts of the MC/deployers to look at OSGi specific properties
and understand what is going on.
2) The feature should be available to all deployments.

[thomas.diesler]

Ok, here is the issue

https://jira.jboss.org/jira/browse/JBDEPLOY-225