Gertjan van Oosten ha scritto:
As quoted from aaime@anonymised.com:
Yet, GeoServer is meant to be forward compatible so GeoServer 1.6.x should
be able to load a GeoServer 1.5.x data directory without issues (if you
find one, it's a bug).
Anyways, out of the top of my head:
* the logging subsystem configuration changed
Indeed. Requires you to modify services.xml.
Requires is an overstatement. I've just started GeoServer 1.6.0 beta4
against the same data directory we shipped along with GeoServer 1.5.3
and it started up just fine, I did not have to change anything relating
to logs. GeoServer would store the log configuration in the new format
as soon as you save it. The only thing is that the old logging level
is lost and GeoServer would fall back on the default one.
Added an issue to document this better for the 1.6.0 release:
http://jira.codehaus.org/browse/GEOS-1502
* the user/access privilege managemnet is in the security/user.properties
and security/services.properties (and there is no UI for that)
Indeed, even though the <adminUserName> is still in services.xml it is
not being used. It should be taken out, and furthermore the user must
change security/users.properties to set the right admin username and
password.
Right, I did not notice this. Thanks for reporting.
Scheduled a couple of issues on this one:
http://jira.codehaus.org/browse/GEOS-1500
http://jira.codehaus.org/browse/GEOS-1499
That's what I do remember... anything to add? 
Yes I have:
- the connection parameters for (at least) a shapefile datastore have
changed:
* the connection parameter that used to have name = "shapefile url"
has now name = "url"
Hmmm.... I looked into 1.5.3 and 1.4.1 data dirs and they do use "url" both. Yet at some time we have had "shapefile url" all right, I still
have some random data dir with those ones.
Did some svn forensics, the old indexed shapefile datastore used in
fact "shapefile url" but when Jody merged it back to the shapefile
datastore (rev 26202, gt2) he renamed it back to "url" for consistency
with the "normal" shapefile datastore.
I guess the only workaround is to place an ugly "if "shapefile url"
then "url"" in the config reading code...
http://jira.codehaus.org/browse/GEOS-1501
* it appears to require a connection parameter like
<parameter value = "ISO-8859-1" name = "charset" />
That attribute is not there in the 1.5.3 data dir that I succesfully
opened. So it's not required as far as I can see.
Then a minor annoyance: the order of the attributes on e.g. <namespace> or
<style> n catalog.xml seems to change randomly between GeoServer releases.
E.g. GeoServer 1.5.1 had <style id = "x" filename = "x.sld" />,
1.5.4a has <style filename = "x.sld" id = "x" /> and 1.6.0-beta4 has <style id = "gshhs_c_land" filename = "gshhs_c_land.sld" />
(IIRC).
That's not a functional change, but it made it more difficult to see
what had actually been changed when I was hunting down why 1.6.0 didn't
pick up my data dir correctly.
Attributes are being stored into a hasmap before being written, and hashmaps are not order preserving... so whatever code
change we may put in, it's not going to give you back the order you had.
Anyways, the config subsystem is going to be replaced, so we're not
going to put any effort in the current one any more (when we move
to a new config subsystem the file format will change completely
and we'll upgrade GeoServer version number to 2).
Cheers
Andrea
