> Hi, I'd like to work out whether it is possible to use Spring-DM
> without enforcing a start order. Specifically the spring-osgi-core
> bundle must be started before the extender because of XML schema
> handling.
> If the extender starts before spring-osgi-core then the following
> exception is thrown for ALL Spring-powered bundles:
> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 3 in XML document from URL [bundleentry://33.fwk32380043/META-INF/
> spring/spring-beans.xml] is invalid; nested exception is
> org.xml.sax.SAXParseException: schema_reference.4: Failed to read
> schema document 'http://www.osgi.org/xmlns/blueprint/v1.0.0/
> blueprint.xsd', because 1) could not find the document; 2) the
> document could not be read; 3) the root element of the document is not
> <xsd:schema>.
> However, if spring-osgi-core is started before the extender then
> everything works fine.
> It seems that the handler registrations from META-INF/spring.handlers
> in spring-osgi-core must be processed before the extender can start,
> why doesn't the extender just force spring-osgi-core to start before
> it begins processing Spring-powered bundles?
> Many thanks,
> Neil