[jboss-dev-forums] [JBoss OSGi Development] - Re: Autostart bundles when deployed in JBossAS

[adrian@jboss.org]

I'm not really following what this is all about?

I don't think you should wrap and replace the DeployersImpl, that is very hacky.
You should just extend it and configure your version as the impl to use.

But even then, it doesn't look very good.
e.g. This certainly looks very wrong.
http://anonsvn.jboss.org/repos/jbossas/projects/demos/microcontainer/trunk/igloo/src/main/java/org/jboss/demos/bootstrap/igloo/deployers/BundleStartStopDeployer.java

It says anything that has an OSGiBundleState (which is everything -
an OSGiMetaData attachment is what determines an OSGi deployment)
should instantly move to INSTALLED at some unknown point in the CLASSLOADER
stage of deployment - you don't even order after the java.lang.ClassLoader attachment?

This completely breaks the "width first" behaviour of the deployers.

If you just want all the bundles started then why not just set the required stage to INSTALLED in the first place? But this is actually not what it is says in the spec.

If there are missing dependencies for something you want started, 
then you don't want to "after the fact" change the required state to DESCRIBED because then it won't appear in the IncompleteDeploymentException.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255161#4255161

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4255161