[JBoss JIRA] Created: (JBOSGI-148) Autostart bundles when deployed in JBossAS
by Thomas Diesler (JIRA)
Autostart bundles when deployed in JBossAS
------------------------------------------
Key: JBOSGI-148
URL: https://jira.jboss.org/jira/browse/JBOSGI-148
Project: JBoss OSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Integration (JBoss)
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: Framework 1.0.0 Alpha1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Assigned: (JBOSGI-5) OSGi Deployers
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBOSGI-5?page=com.atlassian.jira.plugi... ]
Thomas Diesler reassigned JBOSGI-5:
-----------------------------------
Assignee: Thomas Diesler (was: Adrian Brock)
> OSGi Deployers
> --------------
>
> Key: JBOSGI-5
> URL: https://jira.jboss.org/jira/browse/JBOSGI-5
> Project: JBoss OSGi
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Adrian Brock
> Assignee: Thomas Diesler
> Fix For: Framework 1.0.x
>
>
> Holder task for OSGi aspectized deployers.
> The deployers will include at least:
> 1) Structure deployer to recognise OSGi bundles and setup "subdeployments" according to the jars
> specified in the osgi classpath.
> 2) OSGi parser deployer that turns the manifest entries into an OSGIMetaData model
> 3) DeploymentResolver that sets up the dependencies for deployments
> 4) OSGi classloader deployer - replacement for UCL classloader with OSGi classloading semantics
> 5) OSGi real deployer - creates a bean that provides an OSGi facade (the lifecycle)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months