Adapt the URLHandlers for the 4.0 refactoring
---------------------------------------------
Key: FELIX-3302
URL: https://issues.apache.org/jira/browse/FELIX-3302
Project: Felix
Issue Type: Bug
Components: Framework
Affects Versions: framework-4.0.2, framework-4.0.1, framework-4.0.0
Environment: Windows XP (32-bit), Java 6, Weblogic 10gR3, Spring
3.0.5, and Eclipse Gemini Blueprint 1.0.0-RC1.
Reporter: Richard A. Steele
Priority: Critical
See http://markmail.org/message/gby3k46mqcjjpmjm for a full discussion of the
issue, but to summarize:
We are developing a solution around Felix, version 4.0.0, where Felix is
embedded inside of a war deployed as an ear on Weblogic. Everything works very
nicely when we deploy just one of our ears to Weblogic, but with more than one
we're getting an error:
org.springframework.beans.factory.BeanDefinitionStoreException: IOException
parsing XML document from OSGi
resource[bundle://36.0:0/OSGI-INF/blueprint/blueprint-context.xml|bnd.id=36|bnd.sym=com.foo.mapper];
nested exception is java.io.IOException: No framework context found at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:341)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
at
org.eclipse.gemini.blueprint.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:170)
at
org.eclipse.gemini.blueprint.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:141)
at
org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
at
org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:468)
at
org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$800(AbstractDelegatedExecutionApplicationContext.java:60)
at
org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$3.run(AbstractDelegatedExecutionApplicationContext.java:242)
at
org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at
org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.startRefresh(AbstractDelegatedExecutionApplicationContext.java:220)
at
org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.stageOne(DependencyWaiterApplicationContextExecutor.java:224)
at
org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.refresh(DependencyWaiterApplicationContextExecutor.java:178)
at
org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.refresh(AbstractDelegatedExecutionApplicationContext.java:158)
at
org.eclipse.gemini.blueprint.extender.internal.activator.LifecycleManager$1.run(LifecycleManager.java:222)
at java.lang.Thread.run(Thread.java:619) Caused by: java.io.IOException: No
framework context found at
org.apache.felix.framework.URLHandlersBundleStreamHandler.openConnection(URLHandlersBundleStreamHandler.java:82)
at java.net.URL.openConnection(URL.java:945) at
org.eclipse.gemini.blueprint.io.OsgiBundleResource.getInputStream(OsgiBundleResource.java:181)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:328)
... 17 more
The problem appears to be that the URLHandlers installed by Felix does not
allow for multiple instances of Felix to be running in the same VM as separate
(web application) deployments.
The conclusion is "we forgot to adapt the URLHandlers during the 4.0
refactoring."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
