Looks like you tried to resolve a class from a package not imported, so that's why you got a ClassNotFound exception. Since you explicitly imported that sub package it is accessible now.
regards, Achim 2014-03-13 21:36 GMT+01:00 asookazian2 <[email protected]>: > I apparently fixed this problem by adding the following lines in the > Import-Package of the MANIFEST.MF (by hand, I'm not using > maven-bundle-plugin and javax.xml.transform was already existing so I only > added the last 2): > > ,javax.xml.transform > ,javax.xml.transform.dom > ,javax.xml.transform.stream > > before this I didn't have the last 2 lines. So how was it working before > and exactly what is the scenario here? I'd like to understand how/why this > fixed the problem. thx. > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/potential-classpath-or-classloading-issue-with-OSGi-ified-WAR-mega-bundle-tp4032245p4032247.html > Sent from the Karaf - User mailing list archive at Nabble.com. > -- 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/> Software Architect / Project Manager / Scrum Master
