have server able to start up with missing data directories, or with no data directory at all

Andrea Aime added a comment - 04/Dec/09 5:12 AM How is the new configuration subsystem behaving in this respect?

Justin Deoliveira added a comment - 14/Dec/09 1:07 PM It will do the same... BOOM! Should not be hard to fix though, just a few checks in GeoServerLoader. The persistence should work find as the user adds workspaces, datastores, etc...

Andrea Aime added a comment - 28/Jan/12 2:20 PM I believe this one has been fixed in the meantime?

Justin Deoliveira added a comment - 30/Jan/12 10:55 AM Somewhat, the behaviour is the following: 1. If the data dir points to an "empty" directory, ie one that doesn't contain the contents of a data directory then those contents will be created. 2. If the data dir points to a non existent directory it is essentially ignored, falling back on environment variable, etc... and finally usually falling back on the embedded data directory within the webapp root. ANyways, no more kaboom, so i would be fine with closing this one.

Andrea Aime added a comment - 02/Feb/12 7:22 AM - edited Doh, just tried it out for reasons unrelated to this jira and found the startup crashes. 02 feb 14:16:43 ERROR [mortbay.log] - Nested in org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'gwcCatalogConfiguration' defined in URL [jar:file:/home/aaime/.m2/repository/org/geoserver/gwc/2.2-SNAPSHOT/gwc-2.2-SNAPSHOT.jar!/geowebcache-geoserver-context.xml]: Cannot resolve reference to bean 'wms' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'wms' defined in URL [jar:file:/home/aaime/.m2/repository/org/geoserver/wms/2.2-SNAPSHOT/wms-2.2-SNAPSHOT.jar!/applicationContext.xml]: Cannot resolve reference to bean 'geoServer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'geoServer' defined in URL [jar:file:/home/aaime/.m2/repository/org/geoserver/main/2.2-SNAPSHOT/main-2.2-SNAPSHOT.jar!/applicationContext.xml]: Initialization of bean failed; nested exception is java.lang.RuntimeException: java.lang.NullPointerException: java.lang.NullPointerException at org.geoserver.config.GeoServerLoader.readConfiguration(GeoServerLoader.java:629) at org.geoserver.config.DefaultGeoServerLoader.loadGeoServer(DefaultGeoServerLoader.java:68) at org.geoserver.config.GeoServerLoader.postProcessBeforeInitialization(GeoServerLoader.java:131) at org.geoserver.config.GeoServerLoaderProxy.postProcessBeforeInitialization(GeoServerLoaderProxy.java:54) The error is due to some code like this one: File workspaces = resourceLoader.find( "workspaces" ); for (File dir : workspaces.listFiles()) { I guess we should really have a test in web-app that tries the startup in those conditions (fully empty data dir)

Andrea Aime added a comment - 02/Feb/12 7:25 AM Btw, at first I thought it was related to GWC since the error says gwcCatalogConfiguration fails to be created, but after looking better at the stack traces it seems the problem happens the same way without it, just while creating a different bean (but same stack trace in the end)

Justin Deoliveira added a comment - 03/Feb/12 10:25 AM Right, looks like the workspace specific settings stuff is causing this... should be an easy fix.