4:39 a.m.
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
5:04 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-148) Autostart bundles when deployed in JBossAS
[
https://jira.jboss.org/jira/browse/JBOSGI-148?page=com.atlassian.jira.plu...
]
Thomas Diesler updated JBOSGI-148:
----------------------------------
JBoss Forum Reference:
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4253529
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
5:12 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-148) Autostart bundles when deployed in JBossAS
[
https://jira.jboss.org/jira/browse/JBOSGI-148?page=com.atlassian.jira.plu...
]
Thomas Diesler updated JBOSGI-148:
----------------------------------
Attachment: jbosgi142-bundleX.jar
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
Attachments: jbosgi142-bundleA.jar, jbosgi142-bundleX.jar
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
5:12 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-148) Autostart bundles when deployed in JBossAS
[
https://jira.jboss.org/jira/browse/JBOSGI-148?page=com.atlassian.jira.plu...
]
Thomas Diesler updated JBOSGI-148:
----------------------------------
Attachment: jbosgi142-bundleA.jar
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
Attachments: jbosgi142-bundleA.jar, jbosgi142-bundleX.jar
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
5:19 a.m.
New subject: [JBoss JIRA] Commented: (JBOSGI-148) Autostart bundles when deployed in JBossAS
[
https://jira.jboss.org/jira/browse/JBOSGI-148?page=com.atlassian.jira.plu...
]
Thomas Diesler commented on JBOSGI-148:
---------------------------------------
To reproduce
#1 Build the installer
mvn -Pdistro clean install
#2 Install MC Framework in jboss-5.2.0 minimal
#3 Delete default bundles
rm -rf server/minimal/deploy/osgi
#4 Start the server
12:12:55,287 INFO [OSGiBundleManager] JBossOSGi Runtime - Microcontainer
12:12:55,288 INFO [OSGiBundleManager] 1.0.2-SNAPSHOT
12:12:55,293 INFO [FrameworkEventsPluginImpl] Bundle STARTING:
Bundle{system.bundle:0.0.0}
12:12:55,335 INFO [FrameworkEventsPluginImpl] Service REGISTERED: Service{id=1
bundle=system.bundle:0.0.0 classes=[org.jboss.osgi.spi.service.MicrocontainerService]}
12:12:55,400 INFO [FrameworkEventsPluginImpl] Service REGISTERED: Service{id=2
bundle=system.bundle:0.0.0 classes=[org.osgi.service.packageadmin.PackageAdmin]}
12:12:55,404 INFO [FrameworkEventsPluginImpl] Service REGISTERED: Service{id=3
bundle=system.bundle:0.0.0 classes=[org.osgi.service.startlevel.StartLevel]}
12:12:55,407 INFO [FrameworkEventsPluginImpl] Bundle STARTED:
Bundle{system.bundle:0.0.0}
12:12:55,409 INFO [FrameworkEventsPluginImpl] Framwork STARTED
12:12:55,664 INFO [ProfileServiceBootstrap] Loading profile:
ProfileKey@3c4c33[domain=default, server=default, name=minimal]
12:12:55,666 INFO [AbstractServer] Started: JBoss Server[5.2.0.Beta1 (build:
SVNTag=JBoss_5_2_0_Beta1 date=200909022330)] in 14s:470ms
#5 Deploy Bundle jbosgi142-bundleA.jar
12:16:15,779 INFO [FrameworkEventsPluginImpl] Bundle INSTALLED:
Bundle{jbosgi142-bundleA:0.0.0}
12:16:15,938 INFO [OSGiBundleResolverDeployer] Unresolved:
Bundle{jbosgi142-bundleA:0.0.0}
#6 Deploy Bundle jbosgi142-bundleX.jar
12:16:50,849 INFO [FrameworkEventsPluginImpl] Bundle INSTALLED:
Bundle{jbosgi142-bundleX:0.0.0}
12:16:50,968 INFO [FrameworkEventsPluginImpl] Bundle RESOLVED:
Bundle{jbosgi142-bundleX:0.0.0}
12:16:50,973 INFO [FrameworkEventsPluginImpl] Bundle RESOLVED:
Bundle{jbosgi142-bundleA:0.0.0}
12:16:50,975 INFO [FrameworkEventsPluginImpl] Bundle STARTING:
Bundle{jbosgi142-bundleX:0.0.0}
12:16:50,975 INFO [FrameworkEventsPluginImpl] Bundle STARTED:
Bundle{jbosgi142-bundleX:0.0.0}
12:16:50,977 INFO [FrameworkEventsPluginImpl] Bundle STARTING:
Bundle{jbosgi142-bundleA:0.0.0}
12:16:50,988 INFO [FrameworkEventsPluginImpl] Bundle STARTED:
Bundle{jbosgi142-bundleA:0.0.0}
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
Attachments: jbosgi142-bundleA.jar, jbosgi142-bundleX.jar
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
9:36 a.m.
New subject: [JBoss JIRA] Resolved: (JBOSGI-148) Autostart bundles when deployed in JBossAS
[
https://jira.jboss.org/jira/browse/JBOSGI-148?page=com.atlassian.jira.plu...
]
Thomas Diesler resolved JBOSGI-148.
-----------------------------------
Resolution: Done
Done
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
Attachments: jbosgi142-bundleA.jar, jbosgi142-bundleX.jar
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
6063
days inactive
6075
days old
jboss-osgi-issues@lists.jboss.org
5 comments
1 participants
participants (1)
-
Thomas Diesler (JIRA)