Hello
I have just started the process to migrate from GeoServer
1.6.3 to 1.7.2. Using the configuration from 1.6.3 I initially
got a null pointer exception which I tracked down to <maxFeatures>
in services.xml (not present in my 1.6.3 config, apparently
mandatory in 1.7.2).
When I located this problem, I noticed that GeoServer was using
a class LegacyConfigurationImporter. That sounds to me as if
1.7.2 expects a different configuration format. However, I cannot
find any structural differences between my 1.6.3 config and
the default config in the 1.7.2 geoserver.war.
So, is there a new config format, and if so, where can I find
documentation of this?
--
Nils Weinander | Systems Designer
Phone +46 (0)8 410 064 56
Mobile +46 (0)70 978 28 37
--
Curalia AB | www.curalia.se
Hudiksvallsgatan 4, 113 30 Stockholm, Sweden
--
Nils Weinander wrote:
Hello
I have just started the process to migrate from GeoServer
1.6.3 to 1.7.2. Using the configuration from 1.6.3 I initially
got a null pointer exception which I tracked down to <maxFeatures>
in services.xml (not present in my 1.6.3 config, apparently
mandatory in 1.7.2).
When I located this problem, I noticed that GeoServer was using
a class LegacyConfigurationImporter. That sounds to me as if
1.7.2 expects a different configuration format. However, I cannot
find any structural differences between my 1.6.3 config and
the default config in the 1.7.2 geoserver.war.
No new format today, we'll have one in GeoServer 2.0, and
that class represents a sort of a step towards moving to
a new format and a new set of catalog/config classes.
Please open a jira issue (jira.codehaus.org) for the issue
you've found, and every other you might find,
so that we can track it and eventually fix it.
Cheers
Andrea
Andrea Aime wrote:
Nils Weinander wrote:
Hello
I have just started the process to migrate from GeoServer
1.6.3 to 1.7.2. Using the configuration from 1.6.3 I initially
got a null pointer exception which I tracked down to <maxFeatures>
in services.xml (not present in my 1.6.3 config, apparently
mandatory in 1.7.2).
When I located this problem, I noticed that GeoServer was using
a class LegacyConfigurationImporter. That sounds to me as if
1.7.2 expects a different configuration format. However, I cannot
find any structural differences between my 1.6.3 config and
the default config in the 1.7.2 geoserver.war.
No new format today, we'll have one in GeoServer 2.0, and
that class represents a sort of a step towards moving to
a new format and a new set of catalog/config classes.
Ah! thanks.
Please open a jira issue (jira.codehaus.org) for the issue
you've found, and every other you might find,
so that we can track it and eventually fix it.
Done:
http://jira.codehaus.org/browse/GEOS-2640
I have labelled it as a bug, but written in the description
that I'm not sure if it is a bug or just something that
needs to be documented.
--
Nils Weinander | Systems Designer
Phone +46 (0)8 410 064 56
Mobile +46 (0)70 978 28 37
--
Curalia AB | www.curalia.se
Hudiksvallsgatan 4, 113 30 Stockholm, Sweden
--