[jboss-osgi-issues] [JBoss JIRA] Updated: (JBOSGI-340) Autostart bundles when deployed in JBossAS

Thomas Diesler (JIRA) jira-events at lists.jboss.org
Thu Jun 10 11:57:38 EDT 2010


     [ https://jira.jboss.org/browse/JBOSGI-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler updated JBOSGI-340:
----------------------------------

    Description: 
The current workaround is to wrap the deployers

  <bean name="OSGiDeployersWrapper" class="org.jboss.osgi.framework.deployers.OSGiDeployersWrapper" >
    <constructor>
      <parameter><inject bean="MainDeployer"/></parameter>
      <parameter><inject bean="OSGiBundleManager"/></parameter>
    </constructor>
  </bean>

This wrapper should be removed. 

  was:
The basic issue is that a bundle deployment when put in 

OSGiBundleStateDeployer

    requiredStage = DeploymentStages.DESCRIBE

it will only progress to Bundle.INSTALLED, hence the bundle with not resolve nor start.

When requiredStage = DeploymentStages.CLASSLOADER or above, the bundle can start when all its dependencies are resolved.
The bundle deployment will however fail. if it has unresolved dependencies.

The desired behaviour is:

Bundles with unresolved dependencies get INSTALLED without error.
Bundles with resolved dependencies get STARTED without error.
A bundle that could only get INSTALLED (but not RESOLVED) gets STARTED when it's dependencies can be RESOLVED.




> Autostart bundles when deployed in JBossAS
> ------------------------------------------
>
>                 Key: JBOSGI-340
>                 URL: https://jira.jboss.org/browse/JBOSGI-340
>             Project: JBoss OSGi
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Integration (JBoss)
>            Reporter: Thomas Diesler
>            Assignee: Thomas Diesler
>             Fix For: JBossOSGi 1.0.0 Beta4
>
>
> The current workaround is to wrap the deployers
>   <bean name="OSGiDeployersWrapper" class="org.jboss.osgi.framework.deployers.OSGiDeployersWrapper" >
>     <constructor>
>       <parameter><inject bean="MainDeployer"/></parameter>
>       <parameter><inject bean="OSGiBundleManager"/></parameter>
>     </constructor>
>   </bean>
> This wrapper should be removed. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-osgi-issues mailing list