Well if you take a look at the OSGi spec it is allowed only to alter the WebApp-Context for a WAB and that's what actually is working, all other Manifest entries need to be kept the way they are specified in the Manifest. Therefore it works as specified/designed. And my personal opinion as the Bundle-SymbolicName is something to identify a Bundle with it shouldn't be even thought of changing the Bundle-SymbolicName or something the like, it's the same for the Maven location it has to be unique. If you require to run the same bundle twice, either install two different versions of it, or create two seperate Bundles with each having a unique Maven location.
regards, Achim 2013/5/8 Gražvydas Valeika <[email protected]> > Hi, > > Ensure you have a quote for the 'webbundle:path…' >> Something like >> install -s >> 'webbundle:file:///home/gv/work/experiments/ttt/CamelTest/target/CamelTest.wab?Web-ContextPath=/CT222&Bundle-SymbolicName=CamelTestSymbolicName2' >> >> doesn't help. Doesn't work with > '&Bundle-SymbolicName=CamelTestSymbolicName2' part and works without it. > Causes the same exception. > > G. > -- 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/>
