Boo, actually I resolved that weirdness, that was due to me overriding the default classpath, but when it starts I don't get any beans injected which gives me a sad face.......
Tom On Wed, Jul 29, 2015 at 10:38 PM, Achim Nierbeck <[email protected]> wrote: > Hi Tom, > > I'm not sure what happened to your setup, > but actually that shouldn't be of an issue. > I just tested it and stumbled over another thing. > The latest pax-cdi bundles aren't compatible with Jetty 9.1 and Servlet 3.1 > > I'm gonna look at it. > > regards, Achim > > > > 2015-07-29 18:04 GMT+02:00 Tom Barber <[email protected]>: > >> Hello chaps >> >> Running Karaf 4 and PAX CDI I'm running into an issue wiring it all up. I >> have >> >> Require-Capability: org.ops4j.pax.cdi.extension; filter:="(&(extension=p >> ax-cdi-extension)(version>=0.12)(!(version>=0.13)))",osgi.extender; fil >> ter:="(osgi.extender=pax.cdi)" >> >> In my Manifest but when it starts it complains of stuff like: >> >> Caused by: java.lang.ClassNotFoundException: >> WEB-INFes.com.mytool.filemanager.websocket.FileManagerObj not found by >> com.mytool.filemanager-client >> >> Which is weird, mostly because where does WEB-IFes come from? >> >> Anyway I can't work it out, where those errors come from and whilst my >> bundle does come up my beans aren't injected, does anyone have a good idea? >> >> Thanks >> >> Tom >> > > > > -- > > 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 > >
