Community
Participate
Working Groups
Build Identifier: When using Gemini Blueprint without "-Dorg.eclipse.gemini.blueprint.ns.bundles.started=true" the NamespaceBundleLister is created for monitor RESOLVED bundles, but the loaded Bundles still get only added to the NamespaceManager when they are ACTIVE (started). This way some Bundles never get scanned by the NamespaceManager for the schema files (spring.handlers, spring.schemas). Reproducible: Didn't try Steps to Reproduce: 1. use a schema like http://www.springframework.org/schema/osgi http://www.springframework.org/schema/osgi/spring-osg in your bundles context 2. start the framework without setting "-Dorg.eclipse.gemini.blueprint.ns.bundles.started=true" 3. see resolution of the namespace failing because org.eclipse.gemini.blueprint.core was not started when the extender is activated and never will get resolved again.
Created attachment 199176 [details] The first patch
Created attachment 199177 [details] The cleaned first patch (not reformatted the source)
Thanks - however by setting the properties you are requesting that only bundles in started state are used (instead of just resolved). Since you want the opposite you should not define it or define it as false. However your point out a problem with the already installed bundles which I fixed in trunk.
Released - closing.
