[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-587) Recursive module creation triggered by bundle event
Thomas Diesler created JBOSGI-587:
-------------------------------------
Summary: Recursive module creation triggered by bundle event
Key: JBOSGI-587
URL: https://issues.jboss.org/browse/JBOSGI-587
Project: JBoss OSGi
Issue Type: Bug
Components: Core Framework
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.2.0
{code}
at
org.jboss.as.osgi.service.ModuleLoaderIntegration.addModule(ModuleLoaderIntegration.java:128)
at
org.jboss.osgi.framework.internal.ModuleManagerPlugin.createHostModule(ModuleManagerPlugin.java:298)
at
org.jboss.osgi.framework.internal.ModuleManagerPlugin.addModule(ModuleManagerPlugin.java:196)
at
org.jboss.osgi.framework.internal.ResolverPlugin.addModules(ResolverPlugin.java:253)
at
org.jboss.osgi.framework.internal.ResolverPlugin.applyResolverResults(ResolverPlugin.java:201)
at
org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:121)
at
org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551)
at
org.jboss.osgi.framework.internal.HostBundleRevision.findEntries(HostBundleRevision.java:126)
at
org.jboss.osgi.framework.internal.AbstractBundleState.findEntries(AbstractBundleState.java:443)
at
org.eclipse.gemini.blueprint.extender.internal.support.NamespaceManager.maybeAddNamespaceHandlerFor(NamespaceManager.java:130)
at
org.eclipse.gemini.blueprint.extender.internal.activator.ContextLoaderListener.maybeAddNamespaceHandlerFor(ContextLoaderListener.java:462)
at
org.eclipse.gemini.blueprint.extender.internal.activator.ContextLoaderListener$NamespaceBundleLister.handleEvent(ContextLoaderListener.java:169)
at
org.eclipse.gemini.blueprint.extender.internal.activator.ContextLoaderListener$BaseListener.bundleChanged(ContextLoaderListener.java:137)
at
org.jboss.osgi.framework.internal.FrameworkEventsPlugin.fireBundleEvent(FrameworkEventsPlugin.java:372)
at
org.jboss.osgi.framework.internal.AbstractBundleState.fireBundleEvent(AbstractBundleState.java:198)
at
org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:192)
at
org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:174)
at
org.jboss.osgi.framework.internal.ResolverPlugin.setBundleToResolved(ResolverPlugin.java:277)
at
org.jboss.osgi.framework.internal.ResolverPlugin.applyResolverResults(ResolverPlugin.java:207)
at
org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:121)
at
org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551)
at
org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:232)
at
org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:485)
at
org.jboss.as.osgi.management.BundleResourceHandler.handleOperation(BundleResourceHandler.java:145)
at
org.jboss.as.osgi.management.BundleResourceHandler.executeRuntimeStep(BundleResourceHandler.java:99)
{code}
--
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