[jboss-jira] [JBoss JIRA] (AS7-6054) https://github.com/jbosgi/jboss-as/tree/as5476

https://github.com/jbosgi/jboss-as/tree/as5476 ---------------------------------------------- Key: AS7-6054 URL: https://issues.jboss.org/browse/AS7-6054 Project: Application Server 7 Issue Type: Bug Components: OSGi Affects Versions: 7.2.0.Alpha1 Environment: Windows XP SP2 Oracle JDK 1.6.0_32 Reporter: Ed Roberts I am able to recreate a bundle resolution problem that gives very little help in where the cause lies. We deploy a set of Spring 3.1.1.RELEASE bundles in the bundles directory structure, exposed through the standalone.xml capabilities. Separately, a set of bundles are located in the deployments folder, and they include/use some Spring 3.0.7.RELEASE; e.g. beans and core. The reason for the duplication is because a particular LDAP bundle does not work with the later spring bundles. When I deploy the spring-security-ldap-3.1.1.RELEASE.jar in the deployments folder, I get the following WARNING in the console/log file {code} 2012-11-27 16:24:13,808 WARN [org.jboss.as.osgi](MSC service thread 1-5) JBAS011910: Cannot resolve requirements: [] {code} The cause of the issue was located during a debug session, to be {code} Chain 1: org.springframework.security.ldap [HostBundleRevision[org.springframework.security.ldap:3.1.1.RELEASE]] import: null | export: osgi.wiring.package=org.springframework.beans org.springframework.beans [HostBundleRevision[org.springframework.beans:3.0.7.RELEASE]] Chain 2: org.springframework.security.ldap [HostBundleRevision[org.springframework.security.ldap:3.1.1.RELEASE]] import: null | export: osgi.wiring.package=org.springframework.context.support; uses:=org.springframework.beans org.springframework.context [HostBundleRevision[org.springframework.context:3.1.1.RELEASE]] import: null | export: osgi.wiring.package=org.springframework.beans org.springframework.beans [HostBundleRevision[org.springframework.beans:3.1.1.RELEASE]] {code} It seems that when there are multiple providers of a requirement, the requiring bundle is deemed invalid. That doesn't seem correct. Should it not just choose the first valid provider ? Either way, when the Unresolved Bundles are empty in BundleResolveProcessor, the details of the multiple providers should at least be logged as an ERROR as it prevents the bundle from being successfully resolved.