[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-562) Unable to resolve HostBundleRevision

[Rico Neubauer (JIRA)]

Rico Neubauer created JBOSGI-562:
------------------------------------

             Summary: Unable to resolve HostBundleRevision
                 Key: JBOSGI-562
                 URL: https://issues.jboss.org/browse/JBOSGI-562
             Project: JBoss OSGi
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Core Framework
            Reporter: Rico Neubauer
            Assignee: Thomas Diesler


Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-resolver 2.1.0.Final
There is no component for the resolver, so I add it under core-framework.

Not sure about the conditions, but happens with dynamic class loading.
org.jboss.osgi.resolver.felix.StatelessResolver.ResolveContextDelegate#matches(Requirement, Capability) does check the Requirement for being a HostedRequirement, but does not do the same for the Capability. As result, the cast of Capability to XCapability fails:

{noformat}
Caused by: java.lang.ClassCastException: org.jboss.osgi.resolver.spi.AbstractPackageRequirement cannot be cast to org.apache.felix.resolver.impl.HostedCapability
	at org.jboss.osgi.resolver.felix.StatelessResolver$ResolveContextDelegate.matches(StatelessResolver.java:144)
	at org.apache.felix.resolver.impl.Util.getSatisfyingCapability(Util.java:103)
	at org.apache.felix.resolver.impl.ResolverImpl.toStringBlame(ResolverImpl.java:1723)
	at org.apache.felix.resolver.impl.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1050)
	at org.apache.felix.resolver.impl.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1156)
	at org.apache.felix.resolver.impl.ResolverImpl.resolve(ResolverImpl.java:229)
	at org.apache.felix.resolver.impl.ResolverImpl.resolve(ResolverImpl.java:86)
	at org.jboss.osgi.resolver.felix.StatelessResolver.resolve(StatelessResolver.java:66)
	at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:116)
	at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:120)
	at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551)
	at org.jboss.osgi.framework.internal.FallbackLoader.findInUnresolvedModules(FallbackLoader.java:230)
	at org.jboss.osgi.framework.internal.FallbackLoader.findModuleDynamically(FallbackLoader.java:156)
	at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:85)
	at org.jboss.modules.Module.loadModuleClass(Module.java:535)
	at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
	at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
	at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
	at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
	at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
	at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:247)
	at com.company.sth.ConnectionPool.<init>(ConnectionPool.java:131)
	... 95 more
{noformat}

Will attach a pull request, which fixes the problem.

--
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