OK, I'm resigned to the fact that I'm not going to have time to do this. So my parting thoughts are: 1. OSGi metadata should not extend manifest metadata. Manifest metadata should be a separate thing altogether - there are probably more than one deployment type that might make use of it, and by having OSGi metadata extend manifest metadata, you implcitly disallow more than one deployer to make use of the manifest. Instead the manifest metadata should be transformed into OSGi metadata, which is not implementation-dependent on the manifest (which makes it easier to programmatically generate). 2. Once the above is done, I think this might be easier to accomplish using regex - a simple static method to identify and transform manifest into OSGi metadata. 3. This also leads to the conclusion that there is (again) no point to having an OSGi metadata implementation which is not just a plain bean-style POJO. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210492#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...