August 2010 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] Created: (JBOSGI-378) OSGi Performance Analysis

by David Bosschaert (JIRA)

OSGi Performance Analysis ------------------------- Key: JBOSGI-378 URL: https://jira.jboss.org/browse/JBOSGI-378 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossOSGi 1.0.0 Beta8 Reporter: David Bosschaert Assignee: David Bosschaert Fix For: JBossOSGi 1.0.0 Beta9 The MSC-based OSGi Framework performance must be compared to the MC-based OSGi performance as well as compared to other non-JBoss OSGi Framework performance. This comparison should include Service creation and lookup performance as well as bundle installation and wiring performance. -- 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

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-354) Initial Bundle Start Level initialization is done in the wrong place.

by David Bosschaert (JIRA)

Initial Bundle Start Level initialization is done in the wrong place. --------------------------------------------------------------------- Key: JBOSGI-354 URL: https://jira.jboss.org/browse/JBOSGI-354 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Bosschaert Assignee: David Bosschaert Fix For: JBossOSGi 1.0.0 Beta8 Currently the initial bundle start level is set when bundle.start() is called. This is really too late. You want to know the initial start level when the bundle got installed. There is a test case failure for this, for which a temp workaround has been put into place. The failing test is: http://github.com/jbosgi/jbosgi/blob/master/testsuite/functional/src/test... -- 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

15 years, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBOSGI-361) TCK setup for MSC Core Framework

by Thomas Diesler (JIRA)

TCK setup for MSC Core Framework -------------------------------- Key: JBOSGI-361 URL: https://jira.jboss.org/browse/JBOSGI-361 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta9 -- 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

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-363) Update resolver to Apache Felix-3.0.x

by Thomas Diesler (JIRA)

Update resolver to Apache Felix-3.0.x ------------------------------------- Key: JBOSGI-363 URL: https://jira.jboss.org/browse/JBOSGI-363 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta9 The MSC Framework (as well as the MC Framework) uses our new Standalone OSGi Resolver. The current implementation uses a snapshot of the Apache Felix 2.1.0 code base. This needs to be upgraded to the latest Felix 3.0.x release. -- 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

15 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-362) Integrate the MSC Framework with the Installer

by Thomas Diesler (JIRA)

Integrate the MSC Framework with the Installer ---------------------------------------------- Key: JBOSGI-362 URL: https://jira.jboss.org/browse/JBOSGI-362 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta9 The Standalone Runtime, currently still runs on the MC Framework. The installer needs to be updated to use the MSC Framework instead. We do not offer multiple frameworks, instead we do a switch from MC to MSC. The criteria for the switch is that MSC passes all our enterprise example tests on the Remote Runtime. -- 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

15 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-356) JBoss OSGi has implicit imports

by David Bosschaert (JIRA)

JBoss OSGi has implicit imports ------------------------------- Key: JBOSGI-356 URL: https://jira.jboss.org/browse/JBOSGI-356 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Affects Versions: JBossOSGi 1.0.0 Beta8 Reporter: David Bosschaert I came across this when writing a system test that works on Felix too. The system test creates a bundle that uses the org.osgi.framework and org.jboss.osgi.testing packages. Using jbossmc the test worked without declaring these as imports. In Felix, rightly so, I had to declare them. -- 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

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-355) Get Start Level Configuration with custom XML namespace to work with AS

by David Bosschaert (JIRA)

Get Start Level Configuration with custom XML namespace to work with AS ----------------------------------------------------------------------- Key: JBOSGI-355 URL: https://jira.jboss.org/browse/JBOSGI-355 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Productization Reporter: David Bosschaert Assignee: David Bosschaert Fix For: JBossOSGi 1.0.x The following start level configuration doesn't work in AS: <start-level xmlns="urn:jboss:startlevel:1.0" /> This is because the schema is defined in another MC deployment file which must be processed before the one containing the XML that uses it can be processed. This relates to https://community.jboss.org/thread/153462 -- 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

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-209) Implement resolver preferences

by Thomas Diesler (JIRA)

Implement resolver preferences ------------------------------ Key: JBOSGI-209 URL: https://jira.jboss.org/jira/browse/JBOSGI-209 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Adrian Brock Fix For: JBossOSGi 1.0.x The following list defines the preferences, if multiple choices are possible, in order of decreasing priority: * A resolved exporter must be preferred over an unresolved exporter. * An exporter with a higher version is preferred over an exporter with a lower version. * An exporter with a lower bundle ID is preferred over a bundle with a higher ID. -- 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

15 years, 2 months

1
7
0 / 0

[JBoss JIRA] Created: (JBOSGI-340) Autostart bundles when deployed in JBossAS

by Thomas Diesler (JIRA)

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 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-364) Integrate the MSC Framework with AS7

by Thomas Diesler (JIRA)

Integrate the MSC Framework with AS7 ------------------------------------ Key: JBOSGI-364 URL: https://jira.jboss.org/browse/JBOSGI-364 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta9 Our main focus for OSGi functionality is to make it available in AS. I suggest we integrate early with the AS7 code base to catch issues we might not see otherwise and give AS folks the needed OSGi feedback. -- 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

15 years, 2 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues August 2010