Connecting to a Geoserver 1.3.2 data directory may prevent Geoserver 1.4.0 onwards to start up at all. Apparently, 1.3.2 allowed for no namespace specification in datastores, whilst 1.4.0 pretends it, and makes the whole geoserver crash if it's missing.
Here is a piece of a stack trace:
2007-2-6 16:55:01 org.springframework.web.context.ContextLoader initWebApplicationContext ÑÏÖØ: Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'wfs' defined in URL : Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanInitializationException: Error creating xml config reader; nested exception is org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: there is no namespace defined for datatasore 'gdwy' org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'config' defined in URL : Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanInitializationException: Error creating xml config reader; nested exception is org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: there is no namespace defined for datatasore 'gdwy' org.springframework.beans.factory.BeanInitializationException: Error creating xml config reader; nested exception is org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: there is no namespace defined for datatasore 'gdwy' org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: there is no namespace defined for datatasore 'gdwy' at org.vfny.geoserver.global.xml.XMLConfigReader.loadCatalog(XMLConfigReader.java:300) at org.vfny.geoserver.global.xml.XMLConfigReader.load(XMLConfigReader.java:195) at org.vfny.geoserver.global.xml.XMLConfigReader.<init>(XMLConfigReader.java:145) at org.vfny.geoserver.global.Config.setApplicationContext(Config.java:43) at org.springframework.context.support.ApplicationContextAwareProcessor.postProcessBeforeInitialization(ApplicationContextAwareProcessor.java:84) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:248)
If the spring context initialization fails, the whole geoserver startup fails...
Environment
None
Activity
codehaus
April 10, 2015 at 4:35 PM
CodeHaus Comment From: aaime - Time: Thu, 29 Mar 2007 02:02:53 -0500 ---------------------
<p>This issue has been resolved for one month or more without complaints. Closing it.</p>
codehaus
April 10, 2015 at 4:35 PM
CodeHaus Comment From: aaime - Time: Wed, 7 Feb 2007 03:49:56 -0600 ---------------------
<p>Fixed on 1.4.x, 1.5.x, and trunk</p>
Connecting to a Geoserver 1.3.2 data directory may prevent Geoserver 1.4.0 onwards to start up at all.
Apparently, 1.3.2 allowed for no namespace specification in datastores, whilst 1.4.0 pretends it, and makes the whole geoserver crash if it's missing.
Here is a piece of a stack trace:
2007-2-6 16:55:01 org.springframework.web.context.ContextLoader initWebApplicationContext
ÑÏÖØ: Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'wfs' defined in URL : Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanInitializationException: Error creating xml config reader; nested exception is org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: there is no namespace defined for datatasore 'gdwy'
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'config' defined in URL : Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanInitializationException: Error creating xml config reader; nested exception is org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: there is no namespace defined for datatasore 'gdwy'
org.springframework.beans.factory.BeanInitializationException: Error creating xml config reader; nested exception is org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: there is no namespace defined for datatasore 'gdwy'
org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: org.vfny.geoserver.global.ConfigurationException: there is no namespace defined for datatasore 'gdwy'
at org.vfny.geoserver.global.xml.XMLConfigReader.loadCatalog(XMLConfigReader.java:300)
at org.vfny.geoserver.global.xml.XMLConfigReader.load(XMLConfigReader.java:195)
at org.vfny.geoserver.global.xml.XMLConfigReader.<init>(XMLConfigReader.java:145)
at org.vfny.geoserver.global.Config.setApplicationContext(Config.java:43)
at org.springframework.context.support.ApplicationContextAwareProcessor.postProcessBeforeInitialization(ApplicationContextAwareProcessor.java:84)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:248)
If the spring context initialization fails, the whole geoserver startup fails...