10:30 a.m.
Investigate lazy bundle activation for runtime bundles
------------------------------------------------------
Key: JBOSGI-105
URL: https://jira.jboss.org/jira/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Runtime
Reporter: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta3
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
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
3:38 a.m.
New subject: [JBoss JIRA] Assigned: (JBOSGI-105) Investigate lazy bundle activation for runtime bundles
[
https://jira.jboss.org/jira/browse/JBOSGI-105?page=com.atlassian.jira.plu...
]
Thomas Diesler reassigned JBOSGI-105:
-------------------------------------
Assignee: Thomas Diesler
Investigate lazy bundle activation for runtime bundles
------------------------------------------------------
Key: JBOSGI-105
URL: https://jira.jboss.org/jira/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta3
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
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
3:38 a.m.
New subject: [JBoss JIRA] Work started: (JBOSGI-105) Investigate lazy bundle activation for runtime bundles
[
https://jira.jboss.org/jira/browse/JBOSGI-105?page=com.atlassian.jira.plu...
]
Work on JBOSGI-105 started by Thomas Diesler.
Investigate lazy bundle activation for runtime bundles
------------------------------------------------------
Key: JBOSGI-105
URL: https://jira.jboss.org/jira/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta3
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
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
8:18 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-105) Lazy bundle activation policy for runtime bundles
[
https://jira.jboss.org/jira/browse/JBOSGI-105?page=com.atlassian.jira.plu...
]
Thomas Diesler updated JBOSGI-105:
----------------------------------
Summary: Lazy bundle activation policy for runtime bundles (was: Investigate lazy
bundle activation for runtime bundles)
Lazy bundle activation policy for runtime bundles
-------------------------------------------------
Key: JBOSGI-105
URL: https://jira.jboss.org/jira/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta3
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
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
8:51 a.m.
New subject: [JBoss JIRA] Commented: (JBOSGI-105) Lazy bundle activation policy for runtime bundles
[
https://jira.jboss.org/jira/browse/JBOSGI-105?page=com.atlassian.jira.plu...
]
Thomas Diesler commented on JBOSGI-105:
---------------------------------------
Before lazy activation I see on run.sh -c all
2009-07-10 14:47:58,374 INFO [org.jboss.osgi.felix.framework.FelixIntegration] Installed
bundle [1]: org.osgi.compendium
2009-07-10 14:47:58,400 INFO [org.jboss.osgi.felix.framework.FelixIntegration] Installed
bundle [2]: org.apache.felix.log
2009-07-10 14:47:58,411 INFO [org.jboss.osgi.felix.framework.FelixIntegration] Installed
bundle [3]: jboss-osgi-common
2009-07-10 14:47:58,422 INFO [org.jboss.osgi.felix.framework.FelixIntegration] Installed
bundle [4]: jboss-osgi-hotdeploy
2009-07-10 14:47:58,460 DEBUG [org.jboss.osgi.spi.logging.ExportedPackageHelper]
Exported-Packages: org.apache.felix.log
2009-07-10 14:47:58,538 DEBUG [org.jboss.osgi.spi.logging.ExportedPackageHelper]
Exported-Packages: jboss-osgi-common
2009-07-10 14:47:58,572 DEBUG [org.jboss.osgi.spi.logging.ExportedPackageHelper]
Exported-Packages: jboss-osgi-hotdeploy
2009-07-10 14:47:58,685 INFO [jboss-osgi-common] Installed: jboss-osgi-jndi [5]
2009-07-10 14:47:58,703 INFO [jboss-osgi-common] Installed: jboss-osgi-jmx [6]
2009-07-10 14:47:58,785 INFO [jboss-osgi-common] Installed: jboss-osgi-xml-binding [7]
2009-07-10 14:47:58,814 INFO [jboss-osgi-common] Installed: jboss-osgi-webconsole [8]
2009-07-10 14:47:58,830 INFO [jboss-osgi-common] Installed: org.apache.felix.configadmin
[9]
2009-07-10 14:47:58,900 INFO [jboss-osgi-common] Installed: jboss-osgi-jaxb [10]
2009-07-10 14:47:58,957 INFO [jboss-osgi-common] Installed: org.apache.felix.http.jetty
[11]
2009-07-10 14:47:59,053 INFO [jboss-osgi-common] Installed: jboss-osgi-microcontainer
[12]
2009-07-10 14:47:59,067 INFO [jboss-osgi-common] Installed: org.apache.felix.metatype
[13]
2009-07-10 14:47:59,097 INFO [jboss-osgi-common] Installed: jboss-osgi-common-core [14]
2009-07-10 14:47:59,142 INFO [jboss-osgi-common] Installed: jboss-osgi-apache-xerces
[15]
2009-07-10 14:47:59,726 DEBUG [org.jboss.osgi.spi.logging.ExportedPackageHelper]
Exported-Packages: jboss-osgi-jndi
2009-07-10 14:48:00,218 DEBUG [org.jboss.osgi.spi.logging.ExportedPackageHelper]
Exported-Packages: jboss-osgi-jmx
2009-07-10 14:48:00,391 DEBUG [org.jboss.osgi.spi.logging.ExportedPackageHelper]
Exported-Packages: jboss-osgi-xml-binding
2009-07-10 14:48:00,595 DEBUG [org.jboss.osgi.spi.logging.ExportedPackageHelper]
Exported-Packages: jboss-osgi-webconsole
2009-07-10 14:48:00,695 DEBUG [org.jboss.osgi.spi.logging.ExportedPackageHelper]
Exported-Packages: org.apache.felix.configadmin
2009-07-10 14:48:00,814 DEBUG [org.jboss.osgi.spi.logging.ExportedPackageHelper]
Exported-Packages: jboss-osgi-jaxb
2009-07-10 14:48:00,939 DEBUG [org.jboss.osgi.spi.logging.ExportedPackageHelper]
Exported-Packages: org.apache.felix.http.jetty
2009-07-10 14:48:02,422 DEBUG [org.jboss.osgi.spi.logging.ExportedPackageHelper]
Exported-Packages: jboss-osgi-microcontainer
2009-07-10 14:48:02,457 DEBUG [org.jboss.osgi.spi.logging.ExportedPackageHelper]
Exported-Packages: org.apache.felix.metatype
2009-07-10 14:48:02,459 DEBUG [org.jboss.osgi.spi.logging.ExportedPackageHelper]
Exported-Packages: jboss-osgi-common-core
2009-07-10 14:48:04,760 DEBUG [org.jboss.osgi.spi.logging.ExportedPackageHelper]
Exported-Packages: jboss-osgi-apache-xerces
Lazy bundle activation policy for runtime bundles
-------------------------------------------------
Key: JBOSGI-105
URL: https://jira.jboss.org/jira/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta3
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
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
10:15 a.m.
New subject: [JBoss JIRA] Work stopped: (JBOSGI-105) Lazy bundle activation policy for runtime bundles
[
https://jira.jboss.org/jira/browse/JBOSGI-105?page=com.atlassian.jira.plu...
]
Work on JBOSGI-105 stopped by Thomas Diesler.
Lazy bundle activation policy for runtime bundles
-------------------------------------------------
Key: JBOSGI-105
URL: https://jira.jboss.org/jira/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.x
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
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
10:15 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-105) Lazy bundle activation policy for runtime bundles
[
https://jira.jboss.org/jira/browse/JBOSGI-105?page=com.atlassian.jira.plu...
]
Thomas Diesler updated JBOSGI-105:
----------------------------------
Fix Version/s: JBossOSGi 1.0.x
(was: JBossOSGi 1.0.0 Beta3)
Deferred.
Depends on http://issues.apache.org/jira/browse/FELIX-1317
Lazy bundle activation policy for runtime bundles
-------------------------------------------------
Key: JBOSGI-105
URL: https://jira.jboss.org/jira/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.x
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
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
6:24 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-105) Lazy bundle activation policy for runtime bundles
[
https://jira.jboss.org/jira/browse/JBOSGI-105?page=com.atlassian.jira.plu...
]
Thomas Diesler updated JBOSGI-105:
----------------------------------
Fix Version/s: JBossOSGi 1.0.0
(was: JBossOSGi 1.0.x)
Lazy bundle activation policy for runtime bundles
-------------------------------------------------
Key: JBOSGI-105
URL: https://jira.jboss.org/jira/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
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:42 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-105) Lazy bundle activation policy for runtime bundles
[
https://jira.jboss.org/jira/browse/JBOSGI-105?page=com.atlassian.jira.plu...
]
Thomas Diesler updated JBOSGI-105:
----------------------------------
Fix Version/s: JBossOSGi 1.0.x
(was: JBossOSGi 1.0.0 Beta4)
Lazy bundle activation policy for runtime bundles
-------------------------------------------------
Key: JBOSGI-105
URL: https://jira.jboss.org/jira/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.x
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
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:01 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-105) Lazy bundle activation policy for runtime bundles
[
https://jira.jboss.org/jira/browse/JBOSGI-105?page=com.atlassian.jira.plu...
]
Thomas Diesler updated JBOSGI-105:
----------------------------------
Fix Version/s: Framework 1.0.x
(was: JBossOSGi 1.0.x)
Lazy bundle activation policy for runtime bundles
-------------------------------------------------
Key: JBOSGI-105
URL: https://jira.jboss.org/jira/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: Framework 1.0.x
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
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
2:30 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-105) Lazy bundle activation policy for runtime bundles
[
https://jira.jboss.org/browse/JBOSGI-105?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated JBOSGI-105:
----------------------------------
Fix Version/s: JBossOSGi 1.0.0 Beta10
(was: JBossOSGi 1.0.x)
Lazy bundle activation policy for runtime bundles
-------------------------------------------------
Key: JBOSGI-105
URL: https://jira.jboss.org/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta10
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
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
6:03 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-105) Lazy bundle activation policy for runtime bundles
[
https://jira.jboss.org/browse/JBOSGI-105?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated JBOSGI-105:
----------------------------------
Fix Version/s: JBossOSGi 1.0.0 Beta11
(was: JBossOSGi 1.0.0 Beta10)
Lazy bundle activation policy for runtime bundles
-------------------------------------------------
Key: JBOSGI-105
URL: https://jira.jboss.org/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta11
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
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
7:46 a.m.
New subject: [JBoss JIRA] Commented: (JBOSGI-105) Lazy bundle activation policy for runtime bundles
[
https://issues.jboss.org/browse/JBOSGI-105?page=com.atlassian.jira.plugin...
]
Thomas Diesler commented on JBOSGI-105:
---------------------------------------
Done
Running org.jboss.test.osgi.framework.bundle.activation.BundleActivationTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.441 sec
Lazy bundle activation policy for runtime bundles
-------------------------------------------------
Key: JBOSGI-105
URL: https://issues.jboss.org/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta11
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:48 a.m.
New subject: [JBoss JIRA] Resolved: (JBOSGI-105) Lazy bundle activation policy for runtime bundles
[
https://issues.jboss.org/browse/JBOSGI-105?page=com.atlassian.jira.plugin...
]
Thomas Diesler resolved JBOSGI-105.
-----------------------------------
Fix Version/s: JBossOSGi 1.0.0 Beta10
(was: JBossOSGi 1.0.0 Beta11)
Resolution: Done
Done
https://github.com/jbosgi/jbosgi-framework/commit/436eb1bf9f845334fdb68ac...
Lazy bundle activation policy for runtime bundles
-------------------------------------------------
Key: JBOSGI-105
URL: https://issues.jboss.org/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta10
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:43 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-105) Lazy bundle activation policy for runtime bundles
[
https://issues.jboss.org/browse/JBOSGI-105?page=com.atlassian.jira.plugin...
]
Thomas Diesler updated JBOSGI-105:
----------------------------------
Fix Version/s: JBossOSGi 1.0.0 Beta10
(was: JBossOSGi 1.0.0)
Lazy bundle activation policy for runtime bundles
-------------------------------------------------
Key: JBOSGI-105
URL: https://issues.jboss.org/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta10
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:08 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-105) Lazy bundle activation policy for runtime bundles
[
https://issues.jboss.org/browse/JBOSGI-105?page=com.atlassian.jira.plugin...
]
Thomas Diesler updated JBOSGI-105:
----------------------------------
Issue Type: Feature Request (was: Task)
Lazy bundle activation policy for runtime bundles
-------------------------------------------------
Key: JBOSGI-105
URL: https://issues.jboss.org/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta10
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked
into.
In theory this should bring startup time very close to boot time. i.e. the 'all'
profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without
negatively effecting the startup time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4797
days inactive
5453
days old
jboss-osgi-issues@lists.jboss.org
15 comments
1 participants
participants (1)
-
Thomas Diesler (JIRA)