Hi Martin, can you find out which header Karaf is expecting?
There is some likelihood that this issue is already fixed on master, see http://team.ops4j.org/browse/PAXEXAM-431. Actually, according to the OSGi spec, all OSGi manifest headers are optional, so maybe this issue should be addressed to Karaf and/or Felix. Best regards, Harald 2012/9/4 Martin Lichtin <[email protected]>: > Hi > I'm using paxexam-karaf-container. > The test code seems to be magically put into a bundle and loaded. > However, when trying to view its headers, I get the following error. > > karaf@root> ls 162 > > Bundle 162 provides: > -------------------- > objectClass = org.ops4j.pax.exam.ProbeInvoker > Probe-Signature = PaxExam-cc17232a-95a2-4dea-9f08-632343905642 > service.id = 269 > ---- > objectClass = org.osgi.service.blueprint.container.BlueprintContainer > osgi.blueprint.container.symbolicname = > PAXEXAM-PROBE-693610c7-c192-47b1-b0d4-24e188564e3b > osgi.blueprint.container.version = 0.0.0 > service.id = 277 > karaf@root> headers 162 > > Bundle 162 > ---------- > Error executing command: The header cannot be an empty string. > karaf@root> > > > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
