7:23 a.m.
[
https://issues.jboss.org/browse/JBOSGI-485?page=com.atlassian.jira.plugin...
]
Jye Tucker commented on JBOSGI-485:
-----------------------------------
The forum post at http://community.jboss.org/thread/175431 seems to describe the same
issue ("The service's classloader has no visibility of the requested class")
and has better detail + source to reproduce.
The issue seems to be that the service interface needs to be in the same bundle as the
implementation, or the bundle containing the reference-listeners need to be loaded _after_
the bundle containing the implementation.
Blueprint bundle install
------------------------
Key: JBOSGI-485
URL: https://issues.jboss.org/browse/JBOSGI-485
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework, jboss-osgi-blueprint
Affects Versions: JBossOSGi 1.0.0
Reporter: Andreas Tauber
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.1
Installing blueprint bundles with multilevel service dependency which work fine on
equinox/springDM and felix/aries.
Receiving warning; The service's classloader has no visibility of the requested class
XXX, though the class is exported in OSGI Manifest.
After the warning the following stack trace appears:
20:56:45,939 WARN [FrameworkEventsPlugin] Framework WARNING
org.osgi.framework.ServiceException: Cannot unget factory value
at
org.jboss.osgi.framework.internal.ServiceState.ungetScopedValue(ServiceState.java:195)
at
org.jboss.osgi.framework.internal.ServiceManagerPlugin.ungetService(ServiceManagerPlugin.java:428)
at
org.jboss.osgi.framework.internal.AbstractBundleContext.ungetService(AbstractBundleContext.java:360)
at
org.apache.aries.blueprint.container.ReferenceRecipe.bind(ReferenceRecipe.java:142)
at
org.apache.aries.blueprint.container.ReferenceRecipe.retrack(ReferenceRecipe.java:112)
at
org.apache.aries.blueprint.container.AbstractServiceReferenceRecipe.updateListeners(AbstractServiceReferenceRecipe.java:392)
at
org.apache.aries.blueprint.container.ReferenceRecipe.internalCreate(ReferenceRecipe.java:91)
at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64)
at org.apache.aries.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60)
at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64)
at
org.apache.aries.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:771)
at
org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:742)
at
org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:723)
at
org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:689)
at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64)
at
org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:219)
at
org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:147)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:624)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:315)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:213)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
at
org.jboss.osgi.framework.internal.ServiceState.ungetScopedValue(ServiceState.java:192)
... 27 more
cause the bundles work fine, on the other two deployment enviroments something must be
wrong with jboss osgi impl
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira