The issue is not really that, it is what we were talking about on the other thread. The system bundle is not a real deployment, it effectively represents the bootstrap classloader so it needs to adopt that classloader and use it where the deployment gets used. This is what 3.4 calls the "Framework Classpath". But there are other considerations in the spec such as; 3.8.3 - Parent Delegation - which is actually already worked around by the JDKProvider stuff 3.8.5 - System packages 3.14 - Extension Bundles - although they are optional in the spec If you want to factor out the common code into an AbstractBundleState rather than having OSGiSystemBundle extend OSGiBundleState then go ahead, but do it quickly. ;-) I'm currently looking at the manifest parsing so you are not going to break what I'm working on. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251776#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...