November 2009 - jboss-osgi-issues

[JBoss JIRA] Created: (JBOSGI-208) Update framework dependencies on MC

by Thomas Diesler (JIRA)

Update framework dependencies on MC ----------------------------------- Key: JBOSGI-208 URL: https://jira.jboss.org/jira/browse/JBOSGI-208 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 Beta5 Please provide stable versions for these SNAPSHOTS <version.jboss.classloading>2.0.8-SNAPSHOT</version.jboss.classloading> <version.jboss.deployers>2.0.9-SNAPSHOT</version.jboss.deployers> <version.jboss.kernel>2.2.0-SNAPSHOT</version.jboss.kernel> Please also keep in mind that the framework must run with the binary dependencies currently installed in the supported target containers. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBOSGI-151) Cannot resolve circular dependencies

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBOSGI-151?page=com.atlassian.jira.plu... ] Thomas Diesler updated JBOSGI-151: ---------------------------------- Fix Version/s: JBossOSGi 1.0.x (was: JBossOSGi 1.0.0 Beta4) > Cannot resolve circular dependencies > ------------------------------------ > > Key: JBOSGI-151 > URL: https://jira.jboss.org/jira/browse/JBOSGI-151 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Adrian Brock > Fix For: JBossOSGi 1.0.x > > > Unresolved bundle: Bundle{osgi.cmpn:4.2.0.200907101024} > OSGiPackageRequirement{org.osgi.service.http [1.2.0,2.0.0) OPTIONAL {resolution=optional, version="[1.2,2)"}} > Unresolved bundle: Bundle{org.apache.felix.http.jetty:1.0.1} > OSGiPackageRequirement{org.osgi.util.tracker [1.3.0,?) {version="1.3"}} > OSGiPackageRequirement{org.osgi.service.log [1.3.0,?) {version="1.3"}} > OSGiPackageRequirement{org.osgi.service.cm [1.2.0,?) {version="1.2"}} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBOSGI-151) Cannot resolve circular dependencies

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBOSGI-151?page=com.atlassian.jira.plu... ] Thomas Diesler reopened JBOSGI-151: ----------------------------------- Assignee: Adrian Brock (was: Thomas Diesler) Needs to be looked at at the MC level. The test fails when the external resolver is not installed. > Cannot resolve circular dependencies > ------------------------------------ > > Key: JBOSGI-151 > URL: https://jira.jboss.org/jira/browse/JBOSGI-151 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Adrian Brock > Fix For: JBossOSGi 1.0.x > > > Unresolved bundle: Bundle{osgi.cmpn:4.2.0.200907101024} > OSGiPackageRequirement{org.osgi.service.http [1.2.0,2.0.0) OPTIONAL {resolution=optional, version="[1.2,2)"}} > Unresolved bundle: Bundle{org.apache.felix.http.jetty:1.0.1} > OSGiPackageRequirement{org.osgi.util.tracker [1.3.0,?) {version="1.3"}} > OSGiPackageRequirement{org.osgi.service.log [1.3.0,?) {version="1.3"}} > OSGiPackageRequirement{org.osgi.service.cm [1.2.0,?) {version="1.2"}} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBOSGI-149) Fully implement PackageAdmin

by Ales Justin (JIRA)

[ https://jira.jboss.org/jira/browse/JBOSGI-149?page=com.atlassian.jira.plu... ] Ales Justin commented on JBOSGI-149: ------------------------------------ Added org.jboss.test.osgi.compendium.PackageAdminTestCase where we should track our impl - test per PA method. > Fully implement PackageAdmin > ---------------------------- > > Key: JBOSGI-149 > URL: https://jira.jboss.org/jira/browse/JBOSGI-149 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Fix For: JBossOSGi 1.0.x > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBOSGI-129) Filter behaviour change in r4v42

by Thomas Diesler (JIRA)

Filter behaviour change in r4v42 -------------------------------- Key: JBOSGI-129 URL: https://jira.jboss.org/jira/browse/JBOSGI-129 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Environment: [Bug 1418] https://www.osgi.org/members/bugzilla/show_bug.cgi?id=1418 Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: OSGi Framework 1.0.x Running org.jboss.test.osgi.filter.test.FrameworkUtilFilterUnitTestCase FIXME: verify: Invalid (*=b) FIXME: verify: NoMatch (a=) FIXME: verify: NoMatch (a<= 2) FIXME: verify: NoMatch (a<=2 ) FIXME: verify: NoMatch (a<= ) FIXME: verify: NoMatch (a>= 0) FIXME: verify: NoMatch (a>=0 ) FIXME: verify: NoMatch (a>= ) Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.435 sec Running org.jboss.test.osgi.filter.test.BundleContextFilterUnitTestCase FIXME: verify: Invalid (*=b) FIXME: verify: NoMatch (a=) FIXME: verify: NoMatch (a<= 2) FIXME: verify: NoMatch (a<=2 ) FIXME: verify: NoMatch (a<= ) FIXME: verify: NoMatch (a>= 0) FIXME: verify: NoMatch (a>=0 ) FIXME: verify: NoMatch (a>= ) Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.584 sec -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBOSGI-53) Investigate RequiredState for bundle deployments

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBOSGI-53?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBOSGI-53. ---------------------------------- Fix Version/s: (was: JBossOSGi 1.0.x) Resolution: Out of Date > Investigate RequiredState for bundle deployments > ------------------------------------------------ > > Key: JBOSGI-53 > URL: https://jira.jboss.org/jira/browse/JBOSGI-53 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jboss-osgi-deployers > Reporter: Thomas Diesler > Assignee: Thomas Diesler > > If you don't want the exception then you need to control the "required state" > of the deployment such that it doesn't move to "Installed" and instead remains > the unresolved state (Described?). > There already is a method to change the "required state" of an existing deployment > DeployerClient.change(deploymentName, DeploymentState); > but there's nothing currently that lets you set it at initial deployment, e.g. something like > DeployerClient.deploy(Deployment, DeploymentState); // DOES NOT EXIST -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBOSGI-99) No explicit control over bundle.start()

by Thomas Diesler (JIRA)

No explicit control over bundle.start() --------------------------------------- Key: JBOSGI-99 URL: https://jira.jboss.org/jira/browse/JBOSGI-99 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta3 The BundleStartStopDeployer always tries to resolve a bundle, which prevents test cases to only install a bundle -- 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, 5 months

1
10
0 / 0

[JBoss JIRA] Created: (JBOSGI-202) Allow override of where the bootstrap file comes from

by Adrian Brock (JIRA)

Allow override of where the bootstrap file comes from ----------------------------------------------------- Key: JBOSGI-202 URL: https://jira.jboss.org/jira/browse/JBOSGI-202 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Framework Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossOSGi 1.0.0 Beta5 Add some system properties to override where the bootstrap file comes from in FrameworkFactory. org.jboss.osgi.framework.launch.bootstrapURL - An explicit url org.jboss.osgi.framework.launch.bootstrapPath - A path relative to the context classloader -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-200) Split getParameter(s) calls into getDirective(s) and getAttribute(s)

by Adrian Brock (JIRA)

Split getParameter(s) calls into getDirective(s) and getAttribute(s) -------------------------------------------------------------------- Key: JBOSGI-200 URL: https://jira.jboss.org/jira/browse/JBOSGI-200 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossOSGi 1.0.0 Beta5 The ParamterizedAttribute class has just one method getParameter() for retrieving qualifiers to a path/package. This is inefficient - need to skip over directives when comparing attributes - and can be misleading, e.g. using a directive version:=1.0.0 when an attribute version=1.0.0 should be used. The getParameter(s) methods should be replaced with getAttribute(s) and getDirective(s) methods. -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-178) Support for JBoss TM

by Frederic Conrotte (JIRA)

Support for JBoss TM -------------------- Key: JBOSGI-178 URL: https://jira.jboss.org/jira/browse/JBOSGI-178 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Integration (JBoss) Reporter: Frederic Conrotte I would like to see JBoss TM avaialable for JBoss OSGi framework -- 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, 6 months

2
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues November 2009