Hi Lars, with the command "headers yourBundleId" you can display the OSGi manifest.If no manifest is provided inside your war the manifest will be generated during the deployment.To generate a own manifest during the maven build you can use the felix bundle plugin to generate a WAB(WAR with OSGi manifest). But I think this doesn't matter in this case.
Try the following: - Tell us which karaf version is in use. - Your filepath looks strange. Try to run karaf under C:/karaf/deploy. Does it work? - Check if you can reproduce the behavior with this maven-archetype. mvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes -DarchetypeArtifactId=maven-archetype-webapp -DarchetypeVersion=RELEASE -DgroupId=org.apache.karaf.webapp -DartifactId=webapp -DinteractiveMode=false @Achim If I use a exploded war based on the "maven-archetype-webapp" pax-web can't find the Web-ContextPath inside the manifest header. (Karaf 2.2.8) Regards, Michael 2012/7/30 helander <[email protected]>: > Michael, > > there is no OSGI manifest (it's a "standard" WAR ). > What do you mean by the "command headers ID"? > Which Felix plugin? > > /Lars > > > > Michael Prieß wrote >> >> Seems like there is a problem with the symbolic name. Could you please >> attach the exploded OSGi manifest, the output of the command headers >> ID and the configuration of the felix plugin? >> >> Cheers, >> >> Michael >> >> >> 2012/7/30 helander <lehswe@>: >>> I have created a Jira: >>> >>> https://issues.apache.org/jira/browse/KARAF-1692 >>> >>> /Lars >>> >>> >>> >>> -- >>> View this message in context: >>> http://karaf.922171.n3.nabble.com/Web-application-development-using-unpacked-WAR-tp4025360p4025372.html >>> Sent from the Karaf - User mailing list archive at Nabble.com. >> > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Web-application-development-using-unpacked-WAR-tp4025360p4025381.html > Sent from the Karaf - User mailing list archive at Nabble.com.
