Hi, instead of using war: you should use webbundle since webbundle handles OSGi war (WABs) as you already created and the war: handler will try to create a new Manifest.
regards, Achim Am 29.09.2011 19:10, schrieb bmeyer2:
In SMX 4.3, I'm trying to deploy a WAR file that contains static HTML& SWF files. The MANIFEST consists of the following: Manifest-Version: 1.0 Class-Path: Webapp-Context: [APPNAME] Bundle-ManifestVersion: 2 Bundle-Name: [APPNAME] Bundle-SymbolicName: [APPNAME] Bundle-Version: 1.0.0.qualifier Bundle-ClassPath: .,WEB-INF/classes Bundle-Activator: [PACKAGE].Activator Bundle-Vendor: btu Bundle-RequiredExecutionEnvironment: J2SE-1.5 Import-Package: org.osgi.framework;version="1.3.0" All HTML/SWF files are in WebContent. I've created org.ops4j.pax.web.cfg in SMX_HOME/etc, using port 9093. I've deployed the WAR in 3 ways: 1.) Dropped in SMX_HOME/deploy 2.) osgi:install war:file:///C:/[APPNAME].war 3.) osgi:install war:file:///C:/[APPNAME].war?Webapp-Context=[APPNAME] All 3 methods successfully deploy the bundle -- it's activated with no issues. The HTML file should then be reached at http://localhost:9093/[APPNAME]/index.html, but I get a Jetty page with Error 404 NOT_FOUND. So, at least Jetty is working, but something's up with the jar. Any ideas? Thanks in advance! -- View this message in context: http://servicemix.396122.n5.nabble.com/Issues-with-use-of-deployed-WAR-tp4854031p4854031.html Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
-- -- *Achim Nierbeck* 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/>
