April 2013 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] (JBOSGI-633) Extend Resolver API such that FrameworkWiring.resolveBundles() can report problems

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-633?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-633: ---------------------------------- Fix Version/s: JBossOSGi 2.0.1 (was: JBossOSGi 2.0.0) > Extend Resolver API such that FrameworkWiring.resolveBundles() can report problems > ---------------------------------------------------------------------------------- > > Key: JBOSGI-633 > URL: https://issues.jboss.org/browse/JBOSGI-633 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-638) ClassCircularityError with Aries Blueprint on JDK1.7

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-638?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-638: ---------------------------------- Fix Version/s: JBossOSGi 2.0.1 (was: JBossOSGi 2.0.0) > ClassCircularityError with Aries Blueprint on JDK1.7 > ---------------------------------------------------- > > Key: JBOSGI-638 > URL: https://issues.jboss.org/browse/JBOSGI-638 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Blueprint > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.1 > > > {code} > [tdiesler@localhost jbosgi]$ mvn -Dtest=BlueprintTestCase test > 09:13:24,538 DEBUG [org.jboss.osgi.framework] (Blueprint Extender: 2) Register service: ServiceState{service.id=19, objectClass=[org.jboss.test.osgi.example.blueprint.bundle.ServiceB]} > 09:13:24,537 ERROR [org.jboss.osgi.framework] (Blueprint Extender: 1) JBOSGI011026: Framework Error: org.osgi.framework.ServiceException: Cannot get factory value > at org.jboss.osgi.framework.internal.ServiceStateImpl.getScopedValue(ServiceStateImpl.java:152) > at org.jboss.osgi.framework.internal.ServiceManagerImpl.getService(ServiceManagerImpl.java:266) > at org.jboss.osgi.framework.internal.AbstractBundleContext.getService(AbstractBundleContext.java:475) > at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl.addingService(NamespaceHandlerRegistryImpl.java:101) > at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:932) > at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:864) > at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256) > at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229) > at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:894) > at org.jboss.osgi.framework.internal.FrameworkEventsImpl.fireServiceEvent(FrameworkEventsImpl.java:606) > at org.jboss.osgi.framework.internal.ServiceManagerImpl.registerService(ServiceManagerImpl.java:149) > at org.jboss.osgi.framework.internal.AbstractBundleContext.registerService(AbstractBundleContext.java:383) > at org.apache.aries.blueprint.container.BlueprintContainerImpl$3.run(BlueprintContainerImpl.java:412) > at org.apache.aries.blueprint.container.BlueprintContainerImpl$3.run(BlueprintContainerImpl.java:410) > at java.security.AccessController.doPrivileged(Native Method) > at org.apache.aries.blueprint.container.BlueprintContainerImpl.registerService(BlueprintContainerImpl.java:410) > at org.apache.aries.blueprint.container.ServiceRecipe.register(ServiceRecipe.java:191) > at org.apache.aries.blueprint.container.BlueprintContainerImpl.registerServices(BlueprintContainerImpl.java:670) > at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:339) > at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:242) > at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:722) > Caused by: java.lang.ClassCircularityError: org/apache/aries/blueprint/container/BlueprintContainerImpl$5$1 > at org.apache.aries.blueprint.container.BlueprintContainerImpl$5.combine(BlueprintContainerImpl.java:435) > at java.security.AccessControlContext.goCombiner(AccessControlContext.java:493) > at java.security.AccessControlContext.optimize(AccessControlContext.java:401) > at java.security.AccessController.getContext(AccessController.java:502) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:406) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) > at org.apache.aries.blueprint.container.BlueprintContainerImpl.loadClass(BlueprintContainerImpl.java:391) > at org.apache.aries.blueprint.container.BlueprintRepository.loadClass(BlueprintRepository.java:410) > at org.apache.aries.blueprint.container.GenericType.parse(GenericType.java:113) > at org.apache.aries.blueprint.di.AbstractRecipe.doLoadType(AbstractRecipe.java:168) > at org.apache.aries.blueprint.di.AbstractRecipe.loadType(AbstractRecipe.java:161) > at org.apache.aries.blueprint.container.BeanRecipe.loadClass(BeanRecipe.java:245) > at org.apache.aries.blueprint.container.BeanRecipe.getType(BeanRecipe.java:891) > at org.apache.aries.blueprint.container.BeanRecipe.getInstance(BeanRecipe.java:319) > at org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:802) > at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:783) > at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:106) > at org.apache.aries.blueprint.container.ServiceRecipe.createService(ServiceRecipe.java:280) > at org.apache.aries.blueprint.container.ServiceRecipe.internalGetService(ServiceRecipe.java:247) > at org.apache.aries.blueprint.container.ServiceRecipe.getService(ServiceRecipe.java:349) > at org.apache.aries.blueprint.container.ServiceRecipe$TriggerServiceFactory.getService(ServiceRecipe.java:502) > at org.jboss.osgi.framework.internal.ServiceStateImpl$ServiceFactoryHolder.getService(ServiceStateImpl.java:468) > at org.jboss.osgi.framework.internal.ServiceStateImpl.getScopedValue(ServiceStateImpl.java:141) > ... 28 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-589) Support reference: URLs

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-589?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-589: ---------------------------------- Fix Version/s: JBossOSGi 2.0.1 (was: JBossOSGi 2.0.0) > Support reference: URLs > ----------------------- > > Key: JBOSGI-589 > URL: https://issues.jboss.org/browse/JBOSGI-589 > Project: JBoss OSGi > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core Framework > Affects Versions: JBossOSGi 1.1.1 > Reporter: Harald Wellmann > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.1 > > > While this is not an official OSGi standard, Equinox, Felix and Knopflerfish all support {{reference:file:}} URLs for provisioning bundles in place, without copying them to the OSGi storage area. > This works both for JARs and for directories (exploded bundles), e.g. > {noformat} > reference:file:/path/to/my/bundle.jar > reference:file:target/classes/ > {noformat} > For interoperability of frameworks, it would be useful for JBoss OSGi to support this protocol. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-616) Compliant R5 Core Framework

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-616?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-616. ----------------------------------- Resolution: Done Done in jbosgi-framework-3.0.0.CR10 > Compliant R5 Core Framework > --------------------------- > > Key: JBOSGI-616 > URL: https://issues.jboss.org/browse/JBOSGI-616 > Project: JBoss OSGi > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Labels: roadmap > Fix For: JBossOSGi 2.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-642) Consolidate attachments API

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-642?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-642. ----------------------------------- Resolution: Done Done on jbosg-framework-3.0.0.CR14 and dependencies > Consolidate attachments API > --------------------------- > > Key: JBOSGI-642 > URL: https://issues.jboss.org/browse/JBOSGI-642 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.0 CR1 > > > There are currently two incompatible APIs for attachments. One on Deployment. The other on XResource. This needs to be consolidated and aligned with how this woks in AS -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-642) Consolidate attachments API

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-642?page=com.atlassian.jira.plugin... ] Work on JBOSGI-642 started by Thomas Diesler. > Consolidate attachments API > --------------------------- > > Key: JBOSGI-642 > URL: https://issues.jboss.org/browse/JBOSGI-642 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.0 CR1 > > > There are currently two incompatible APIs for attachments. One on Deployment. The other on XResource. This needs to be consolidated and aligned with how this woks in AS -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-642) Consolidate attachments API

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-642: ------------------------------------- Summary: Consolidate attachments API Key: JBOSGI-642 URL: https://issues.jboss.org/browse/JBOSGI-642 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 2.0.0 CR1 There are currently two incompatible APIs for attachments. One on Deployment. The other on XResource. This needs to be consolidated and aligned with how this woks in AS -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues April 2013