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

[JBoss JIRA] Created: (JBOSGI-337) Document usage of the urn:jboss:pojo2osgi:1.0 namespace

by Thomas Diesler (JIRA)

Document usage of the urn:jboss:pojo2osgi:1.0 namespace ------------------------------------------------------- Key: JBOSGI-337 URL: https://jira.jboss.org/browse/JBOSGI-337 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Ales Justin Fix For: JBossOSGi 1.0.0 Beta8 -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-330) Invalid capability matching for dynamic or optional imports

by Thomas Diesler (JIRA)

Invalid capability matching for dynamic or optional imports ----------------------------------------------------------- Key: JBOSGI-330 URL: https://jira.jboss.org/browse/JBOSGI-330 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 The OSGiPackageCapability requires a workaround in resolve that falls back to simple package name, version and attribute matching if (osgiRequirement.isDynamic() || osgiRequirement.isOptional()) { match = super.resolves(reqModule, mcRequirement); match &= matchAttributes(osgiRequirement); } -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-351) Release 1.0.0.Beta8

by Thomas Diesler (JIRA)

Release 1.0.0.Beta8 ------------------- Key: JBOSGI-351 URL: https://jira.jboss.org/browse/JBOSGI-351 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-143) Implement DynamicImport-Package

by Thomas Diesler (JIRA)

Implement DynamicImport-Package ------------------------------- Key: JBOSGI-143 URL: https://jira.jboss.org/jira/browse/JBOSGI-143 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: Framework 1.0.0 Alpha1 -- 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, 4 months

1
16
0 / 0

[JBoss JIRA] Created: (JBOSGI-138) Proper system BundleContext implementation

by Thomas Diesler (JIRA)

Proper system BundleContext implementation ------------------------------------------ Key: JBOSGI-138 URL: https://jira.jboss.org/jira/browse/JBOSGI-138 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Reporter: Thomas Diesler Fix For: Framework 1.0.0 Alpha1 Currently we have OSGiSystemBundle extends OSGiBundleState which initializes the OSGiBundleState with a null DeploymentUnit All Bundle and BundleContext methods that internally access the DU fail for the system bundle An improved abstraction would be OSGiSystemBundle extends AbstractBundle OSGiBundle extends AbstractBundle -- 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, 4 months

1
11
0 / 0

[JBoss JIRA] Created: (JBOSGI-320) Integrate 3rd party bundle resolver

by Thomas Diesler (JIRA)

Integrate 3rd party bundle resolver ----------------------------------- Key: JBOSGI-320 URL: https://jira.jboss.org/jira/browse/JBOSGI-320 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 Beta8 Integrate the Apache Felix resolver -- 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, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-333) Make it possible to specify the initial start level of the system

by David Bosschaert (JIRA)

Make it possible to specify the initial start level of the system ----------------------------------------------------------------- Key: JBOSGI-333 URL: https://jira.jboss.org/browse/JBOSGI-333 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossOSGi 1.0.0 Beta8 Reporter: David Bosschaert Assignee: David Bosschaert The framework needs to have a way to specify the initial start level that the system will move to. Typically this is done with a framework property like org.osgi.framework.startlevel.beginning -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-335) Ensure that start levels are supported via JMX

by David Bosschaert (JIRA)

Ensure that start levels are supported via JMX ----------------------------------------------- Key: JBOSGI-335 URL: https://jira.jboss.org/browse/JBOSGI-335 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: jboss-osgi-jmx Affects Versions: JBossOSGi 1.0.0 Beta8 Reporter: David Bosschaert Specifing and controlling start levels via JMX should be supported. We need to properly test this. It should be possible to: 1. Install a bundle using JMX 2. Set its start level 3. Start the bundle If the framework's startlevel isn't at the level specified for the bundle, the bundle should not actually be started but marked as 'to-be-started' so that when the framework reaches that start level the bundle will be started. All this functionality is there in the core, but we need to make sure it works properly from JMX. -- 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, 4 months

2
9
0 / 0

[JBoss JIRA] Created: (JBOSGI-310) Link generated javadoc to org.osgi API

by Thomas Diesler (JIRA)

Link generated javadoc to org.osgi API -------------------------------------- Key: JBOSGI-310 URL: https://jira.jboss.org/jira/browse/JBOSGI-310 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 API docs should contain remote links to http://www.osgi.org/javadoc/r4v42/ -- 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, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-350) Add OSGi Alliance trade mark to images in userguide

by Thomas Diesler (JIRA)

Add OSGi Alliance trade mark to images in userguide --------------------------------------------------- Key: JBOSGI-350 URL: https://jira.jboss.org/browse/JBOSGI-350 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 -- 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, 4 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues June 2010