|
| Re: Blueprint: Namespace trouble [message #655561 is a reply to message #655502] |
Mon, 21 February 2011 18:52   |
|
Is this configuration working with another approach, like say, Spring DM?
In the namespace declarations:
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-2.1.xsd
Maybe you should try with:
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context.xsd
or
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd
Usually the namespace XSDs are in the Spring JARs of the related version, registered with both no version and the current version of Spring.
DISCLAIMER: I have no experience with Blueprint or Spring 3.0, I just quickly answer based on my general experience with Spring (2.x), in case this may by chance solve your problem.
Maybe it has absolutely nothing to do with that...
Argeo GmbH (Berlin) - http://www.argeo.org/
|
|
|
| Re: Blueprint: Namespace trouble [message #655581 is a reply to message #655502] |
Mon, 21 February 2011 19:42 |
 David Fogel
Messages: 1
Registered: February 2011 |
Junior Member |
|
|
Like the last poster pointed out, it does seem like you could clean up your namespace declarations.
However, I've had something similar happen in our project (using raw spring DM in equinox), and for us it's a weird, _intermittent_ issue where our app will just fail to start a few times, throwing this same exception, and then finally it will work again. I looked at this in depth a few months back (and I found dozens of useless forum posts with people having similar issues), and although I frustratingly can't remember all the details, I think there's a race condition somewhere such that if the wrong classloader gets checked for the namespace XSD files before the right one is there, then this happens.
Anyhow, my point is that if your project reliably fails with this message, it may be a simple configuration problem, but if it fails sometimes and works other times, then I think you're hitting what we ran into, and I would look at bundle start orderings and that sort of thing.
|
|
|
|
|
|
|
|
|
|
|
| Re: Blueprint: Namespace trouble [message #947655 is a reply to message #718100] |
Wed, 17 October 2012 09:39 |
Sebastian Lorenz
Messages: 42
Registered: November 2010 |
Member |
|
|
Using Blueprint 1.0.2.Release I still get this error if my persistence bundles get restarted at application startup. If I disable bundle refresh with -DREFRESH_BUNDLES=false the error is gone.
Okt 17, 2012 11:21:28 AM org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor fail
Schwerwiegend: Unable to create application context for [com.qualitype.personmanager], unsatisfied dependencies: none
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Unable to locate Spring NamespaceHandler for XML schema namespace [http\://www.springframework.org/schema/osgi]
Offending resource: URL [bundleentry://117.fwk1823840336/META-INF/spring/config.xml]
at org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85)
at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:80)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.error(BeanDefinitionParserDelegate.java:316)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1416)
at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1409)
at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:184)
at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:140)
at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:111)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:493)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:174)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:209)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:180)
at org.eclipse.gemini.blueprint.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:170)
at org.eclipse.gemini.blueprint.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:140)
at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:131)
at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:522)
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:177)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.refresh(AbstractDelegatedExecutionApplicationContext.java:157)
at org.eclipse.gemini.blueprint.extender.internal.activator.LifecycleManager$1.run(LifecycleManager.java:211)
at java.lang.Thread.run(Unknown Source)
Btw: In the error message I added a backslash in the namespace cause I'm not allowed to use links in this forum.
[Updated on: Wed, 17 October 2012 09:41] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.03711 seconds
] 
Search
Help
Register
Login
Home
