Well a RESOLVED state does also mean all Classes which are exported are available to other bundles and all imported packages are as well imported. This actually means resolve ... starting a bundle is only necessary if it actually contains logic which needs to be started, for example an activator, a blueprint definition, or a Declarative Service. If your bundle only contains packages to be exported and used by others RESOLVED is a valid state.
regards, Achim 2016-04-20 10:03 GMT+02:00 Jean-Baptiste Onofré <[email protected]>: > Hi, > > did you try a bundle:start on the reflection bundle ? > > Regards > JB > > > On 04/20/2016 09:58 AM, mdo wrote: > >> Just for future reference: >> >> I had to restart Karaf once again to get it up and running. For unknown >> reasons the reflections bundle was only in state RESOLVED before and >> additionally I had to install javassist. Despite the RESOLVED state >> before, >> my own bundle was able to use the Reflections class but this failed >> internally as described. >> >> Having javassist and the ServiceMix(!) bundle for org.reflections in place >> this is working: >> new Reflections("my.package", MyClass.class.getClassLoader()) >> >> >> >> >> >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/NPE-with-org-reflections-tp4046252p4046297.html >> Sent from the Karaf - User mailing list archive at Nabble.com. >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
