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

[JBoss JIRA] Created: (JBOSGI-146) Runtime does not start on windows/cygwin

by Thomas Diesler (JIRA)

Runtime does not start on windows/cygwin ---------------------------------------- Key: JBOSGI-146 URL: https://jira.jboss.org/jira/browse/JBOSGI-146 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-249) Framework permissions

by Thomas Diesler (JIRA)

Framework permissions --------------------- Key: JBOSGI-249 URL: https://jira.jboss.org/jira/browse/JBOSGI-249 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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, 9 months

1
7
0 / 0

[JBoss JIRA] Created: (JBOSGI-254) Framework security

by Thomas Diesler (JIRA)

Framework security ------------------ Key: JBOSGI-254 URL: https://jira.jboss.org/jira/browse/JBOSGI-254 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-370) Initial support for URLStreamHandlerService

by Thomas Diesler (JIRA)

Initial support for URLStreamHandlerService ------------------------------------------- Key: JBOSGI-370 URL: https://jira.jboss.org/browse/JBOSGI-370 Project: JBoss OSGi Issue Type: Feature Request 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-206) Wire to an already uninstalled bundle

by Thomas Diesler (JIRA)

Wire to an already uninstalled bundle ------------------------------------- Key: JBOSGI-206 URL: https://jira.jboss.org/jira/browse/JBOSGI-206 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-deployers Environment: https://issues.apache.org/jira/browse/FELIX-972 Reporter: Thomas Diesler Assignee: Thomas Diesler Redeployment of bundles seems to fail -- 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

1
17
0 / 0

[JBoss JIRA] Created: (JBOSGI-357) Multiple class-spaces that share the same import doesn't work

by David Bosschaert (JIRA)

Multiple class-spaces that share the same import doesn't work ------------------------------------------------------------- Key: JBOSGI-357 URL: https://jira.jboss.org/browse/JBOSGI-357 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 Attachments: shared.jar, test-1.jar, test-2.jar, versioned-1.jar, versioned-2.jar The following deployment fails: A shared bundle - Exports: org.acme.shared A versioned bundle - Imports: org.acme.shared - Exports: org.acme.versioned;version="1.0" Another versioned bundle - Imports: org.acme.shared - Exports: org.acme.versioned;version="2.0" A test bundle - Imports: org.acme.shared - Imports: org.acme.versioned;version="[1.0,1.0]" Another test bundle - Imports: org.acme.shared - Imports: org.acme.versioned;version="[2.0,2.0]" Deployment of the last bundle fails with the following message: 10:08:29,761 ERROR [AbstractKernelController] Error resolving dependencies for ClassLoader: name=vfs:///tmp/install4049343032016140838.jar/ state=Describe mode=Manual requiredState=ClassLoader java.lang.IllegalStateException: OSGiModule Bundle-Thread_1-1:0.0.0 has a requirement OSGiPackageRequirement{Bundle-Thread_1-1-0.0.0[org.jboss.osgi.test.versioned;version=[2.0,2.0]]} which is inconsistent with OSGiPackageRequirement{Bundle-Thread_1-0-0.0.0[org.jboss.osgi.test.versioned;version=[1.0,1.0]]} from OSGiModule Bundle-Thread_1-0:0.0.0 at org.jboss.classloading.spi.dependency.ClassLoadingSpace.join(ClassLoadingSpace.java:251) at org.jboss.classloading.spi.dependency.ClassLoadingSpace.joinAndResolve(ClassLoadingSpace.java:120) at org.jboss.classloading.spi.dependency.ClassLoadingSpace.joinAndResolve(ClassLoadingSpace.java:169) at org.jboss.classloading.spi.dependency.ClassLoadingSpace.resolve(ClassLoadingSpace.java:337) at org.jboss.classloading.spi.dependency.Module.resolveModule(Module.java:1365) at org.jboss.classloading.spi.dependency.RequirementDependencyItem.resolve(RequirementDependencyItem.java:118) at org.jboss.dependency.plugins.AbstractDependencyInfo.internalResolveDependencies(AbstractDependencyInfo.java:443) at org.jboss.dependency.plugins.AbstractDependencyInfo.resolveDependencies(AbstractDependencyInfo.java:423) at org.jboss.dependency.plugins.AbstractController.resolveDependencies(AbstractController.java:1436) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1400) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1207) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:739) at org.jboss.deployers.plugins.main.MainDeployerImpl.change(MainDeployerImpl.java:732) at org.jboss.osgi.framework.packageadmin.PackageAdminImpl.advanceBundlesToClassloader(PackageAdminImpl.java:415) at org.jboss.osgi.framework.packageadmin.PackageAdminImpl.resolveBundles(PackageAdminImpl.java:389) at org.jboss.osgi.deployment.internal.SystemDeployerService.deploy(SystemDeployerService.java:92) at org.jboss.osgi.framework.service.internal.DeployerServiceImpl.deploy(DeployerServiceImpl.java:96) at org.jboss.osgi.webconsole.internal.plugins.InstallActionExt$1.doRun(InstallActionExt.java:71) at org.apache.felix.webconsole.internal.core.InstallAction$InstallHelper.run(InstallAction.java:340) Note that this works in Felix and Equinox... -- 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
6
0 / 0

[JBoss JIRA] Created: (JBOSGI-282) Review DEBUG level logging volume

by Thomas Diesler (JIRA)

Review DEBUG level logging volume --------------------------------- Key: JBOSGI-282 URL: https://jira.jboss.org/jira/browse/JBOSGI-282 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x http://blogs.jboss.org/blog/dimitris/2005/04/01/AC08547736BD16504BEC955AE... Another factor that isDebugEnabled() has been abused is due to the fact that in many cases we (developers) have used DEBUG for high traffic logging, that should really be TRACE. The reason being, we (developers) are usually lazy to enable the TRACE level in log4j.xml while developing, and we prefer to just use debug() instead, that we know it will work by default! "If the user doesn't like this, she can turn if off", while the idea should really be, "I need to enable TRACE while I do development, and save server.log from being filled up with garbage, and the user from getting lost inside my verbose traces". * ERROR - A definite problem * WARN - Likely a problem, but can live with it * INFO - Common notifications, lifecycle stuff * DEBUG - Low volume debug * TRACE - High volume debug -- 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

1
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-377) Initial XService implementation

by Thomas Diesler (JIRA)

Initial XService implementation ------------------------------- Key: JBOSGI-377 URL: https://jira.jboss.org/browse/JBOSGI-377 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 Beta9 Implement and document how MSC services can access OSGi services and vice versa -- 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
6
0 / 0

[JBoss JIRA] Created: (JBOSGI-374) Release 1.0.0.Beta9

by Thomas Diesler (JIRA)

Release 1.0.0.Beta9 ------------------- Key: JBOSGI-374 URL: https://jira.jboss.org/browse/JBOSGI-374 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 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-331) Start Level TCK Failure: testActivatorChangeBundleStartLevel()

by David Bosschaert (JIRA)

Start Level TCK Failure: testActivatorChangeBundleStartLevel() -------------------------------------------------------------- Key: JBOSGI-331 URL: https://jira.jboss.org/browse/JBOSGI-331 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 The following Start Level Service TCK test fails: org.osgi.test.cases.startlevel.junit.StartLevelControl.testActivatorChangeBundleStartLevel() This is caused by a bundle which increases its own start level in the BundleActivcator.start(). This should cause the bundle to get stopped (on a different thread), but because the starting of the bundle hasn't finished yet the stop() seems to get ignored which causes the test to fail. -- 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, 1 month

2
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues August 2010