thanks for the feedback. Working with non-osgi ready bundles can be a real PITA. That's why there are already a couple of different wrapper projects available. For example there is the Spring repository for OSGi bundle, then there is the ServiceMix wrappers for all kinds of 3rd-party libs take a look at it you probably will find a couple of those you are affected, and last but not least there is the newly created Pax-Tipi project also trying to help out with "wrapping" the "unwilling" 3rd party libs :)
And of course you still are able to do it either yourself or just embed non OSGi jars in your application jar/war (just place them in the lib-folder an make sure bnd knows it while creating your manifest) regards, Achim 2013/1/27 barnesjd <[email protected]> > In case you're interested, I wrote a blog post about how I figured it out: > http://barnesjd.wordpress.com/2013/01/26/noclassdeffounderror-wrong-name/ > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/2-3-0-Deploying-a-war-with-a-listener-in-web-xml-tp4027455p4027493.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 OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
