I've released 0.8.1 last week with the only regression about problems serving static resources. Could you give it a try and see if that's actually the same problem you have ?
On Mon, Nov 22, 2010 at 10:06, Raymond Lai <[email protected]> wrote: > Hi, > > Note sure if it's Pax-web related, but I think I'll post here first. > > Using Pax web 0.8.0 with Apache Karaf. I want to make a war which > serves only static resources - i.e. Javascript files, CSS, images, > etc, and it's intended to be shared between web contexts. However, I > found resources served by this war (which is actually a directory with > name ended with .war) are sometimes inaccessible, i.e. returned with a > 404 error. > > However, if the resources are included with the war containing my web > applications, they will serve fine. I then tried jar the directory as > war, but the result is the same. > > I'm using a web.xml with no listeners/filters/servlets declared; and > my MANIFEST.MF looks like this: > > Bundle-ManifestVersion: 2 > Bundle-Name: my.static.resources > Bundle-SymbolicName: my.static.resources > Webapp-Context: resources > Bundle-Classpath: .,WEB-INF/classes > Import-Package: javax.servlet,javax.servlet.http > > While including the static resources to the war is a stable solution, > I still hope I can make static resources a standalone war for easier > maintenance. Is there anything I missed? > > TIA, > Raymond > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
