Hi, It isn't clear to me exactly what you are trying, so I'll make some assumptions and go from there.
If you have a fragment that puts files in OSGi-INF/blueprint (and the host does not define a Bundle-Blueprint header) then it should be picked up provided that the fragment was attached when the host bundle was started. I do not see a test for this in our backlog, but the CT which has been run does test for this and I believe we pass that test. If you have a fragment that identifies a blueprint file using the Bundle-Blueprint header then it is not processed section 121.3.4 of the blueprint specification says: "A Bundle-Blueprint manifest header specified in a fragment is ignored by the Blueprint Container." If your host bundle had Bundle-Blueprint: META-INF/blueprint/*.xml (to quote from Valentin's example) then it will search both the bundle and fragment for files. Alasdair On 14 March 2011 19:10, PSI-Systems <[email protected]> wrote: >> as I understand the spec (121.3.4) Blueprint should search in >> OSGI-INF/blueprint for blueprint xml files (in both the host and fragments). >> If you want it to locate things in META-INF/blueprint you should be able to >> the Bundle-Blueprint manifest header like: >> >> Bundle-Blueprint: META-INF/blueprint/*.xml >> >> Hope this helps, > I meant OSGI-INF/blueprint, sry. > But only explicitly setting the header in the fragment or the host > bundle worked. > > Sandro > -- Alasdair Nottingham [email protected]
