Hi Achim, Thanks for the advice.
Karaf did indeed help. Automatic deploy didn't seem to work but doing a manual osgi:install the war extender successfully kicked off. It didn't succeed, there must be errors in my MANIFEST.MF, but at least I have an error trace to go from. Regards, Dave On Mon, 2011-04-04 at 09:25 +0200, Achim Nierbeck wrote: > Hi Dave, > > ok, I thought I fixed that, but maybe this is only fixed in trunk :) > > to get it going then I recommend also deploying the spi bundle. > You might also take a look at the integration tests available in the sources > at > > - https://github.com/ops4j/org.ops4j.pax.web > or > - git://github.com/ops4j/org.ops4j.pax.web.git > > I'm using pax exam for integration tests, there you see what kind of > bundles are needed. > If you also are looking for a good container you might take a look at > Apache Karaf, > pax web is included in this and runs out of the box. > > If you need more help don't hesitate to ask :) > > regards, Achim > > > > > 2011/4/3 Dave Reynolds <dave.e.reyno...@gmail.com>: > > I'm having a little trouble getting the Pax Web war extender (1.0.2) to > > work. Probably user error (I'm something of newby to OSGi). > > > > (1) I tried deploying the pax-web-jetty-bundle and pax-web-extender-war. > > The jetty bundle worked fine as an org.osgi.service.http.HttpService but > > the extender-war complained it couldn't resolve the spi. So I modified > > the jetty-bundle MANIFEST.MF to add: > > > > Export-Package: ... ,org.ops4j.pax.web.service.spi;version="1.0.2" > > > > since the SPI does seem to be in the bundle, just not exported. That > > seemed work work fine in that the extender-war starts up. > > > > (2) However, when I deploy my war as a bundle nothing happens, no > > messages, no errors, and the context remains unbound. My war was > > generated from a Ruby Sinatra app using warble. It works OK in tomcat. > > The MANIFEST for the war looks like: > > > > Manifest-Version: 1.0 > > Created-By: Warbler 1.2.1 > > Bundle-ManifestVersion: 2 > > Bundle-SymbolicName: com.epimorphics.ruit.demo > > Bundle-Version: 0.0.1 > > Bundle-ClassPath : > > WEB_INF/lib/jruby-core-1.6.0.jar,WEB_INF/lib/jruby-rack-1.0.8.jar,WEB_INF/lib/jruby-stdlib-1.6.0.jar > > Import-Package: javax.servlet, javax.servlet.http > > Webapp-Context: ruit > > > > The relevant bit of the web.xml is: > > > > <filter> > > <filter-name>RackFilter</filter-name> > > <filter-class>org.jruby.rack.RackFilter</filter-class> > > </filter> > > <filter-mapping> > > <filter-name>RackFilter</filter-name> > > <url-pattern>/*</url-pattern> > > </filter-mapping> > > > > <listener> > > <listener-class>org.jruby.rack.RackServletContextListener</listener-class> > > </listener> > > > > It seems to deploy OK and the OSGi console shows it as having the > > specified class path. Both the listener and filter are in the > > jruby-rack-1.0.8.jar on the classpath. I've tried exporting the > > org.jruby.rack package just in case but that makes no difference. > > > > My environment is Equinox via bndtools under Eclipse (using Sun JVM > > 1.6.0_24 on Ubuntu 10.10 if that makes any difference) with Felix > > bundles for the console, web console, logging etc. I'm deploying the war > > using: > > install file:load/ruit.war > > start <N> > > > > How can I best debug what's going on? Is it possible to get the war > > extender to log what it is doing? > > > > Dave > > > > > > > > > > > > > > _______________________________________________ > > general mailing list > > general@lists.ops4j.org > > http://lists.ops4j.org/mailman/listinfo/general > > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
