[Geoserver-devel] Migration from 1.5.4 to 1.7 using data directory

GeoServer GeoServer Developer
1

http://www.nabble.com/Spring-errors-deploying-1.7-snapshot-geoserver.war-to17835818.html#a17835818
http://www.nabble.com/Spring-errors-deploying-1.7-snapshot-geoserver.war-to17835818.html#a17835818

Hi folks.

My default 1.7 installation works fine (using Tomcat 6.0.18 and the war file
distribution with MySQL plugin) but when I re-configure to my existing
(1.5.4) data configuration using GEOSERVER_DATA_DIR I get the same error
from the above linked post.

The styles, stores and featureTypes all load but then the error is thrown by
the wcsLoader which stops initialization. I don't have any coverages in my
configuration. I'm using the stable release. I've had a look through a few
posts with the same error but can't see any resolution. Has this been
resolved by a later release?

Thanks. Dan

--
View this message in context: http://www.nabble.com/Migration-from-1.5.4-to-1.7-using-data-directory-tp21038287p21038287.html
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

2

Hi Dan,

Which version in particular of 1.7? 1.7.0 or 1.7.1? I just tried accessing a 1.5.x data directory with 1.7.1 and did not have any problems loading up. It could be an entirely different problem but perhaps this has already been fixed.

If you are indeed using 1.7.1 could you include the error log from your startup. Thanks.

-Justin

lunarfish wrote:

http://www.nabble.com/Spring-errors-deploying-1.7-snapshot-geoserver.war-to17835818.html#a17835818
http://www.nabble.com/Spring-errors-deploying-1.7-snapshot-geoserver.war-to17835818.html#a17835818

Hi folks.

My default 1.7 installation works fine (using Tomcat 6.0.18 and the war file
distribution with MySQL plugin) but when I re-configure to my existing
(1.5.4) data configuration using GEOSERVER_DATA_DIR I get the same error
from the above linked post.

The styles, stores and featureTypes all load but then the error is thrown by
the wcsLoader which stops initialization. I don't have any coverages in my
configuration. I'm using the stable release. I've had a look through a few
posts with the same error but can't see any resolution. Has this been
resolved by a later release?

Thanks. Dan

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.