I just put GeoServer 1.0.1 out as a release on sourceforge. Available for
download at http://prdownloads.sf.net/geoserver/geoserver-1.0.1.tar.gz
This is primarily a bug fix release. Fixed up some insert and update
errors, as well as that problem with namespace prefixes in featureid kvps.
See the full list of fixes in the release notes. Special thanks goes to
Doug Cates for his work in finding all sorts of hidden little bugs.
The one addition of interest to developers is experimental support for
Postgis 0.8 with GEOS. It hasn't been officiallly released, but the cvs
version is stable, and taking advantage of it with geoserver was quite
easy. It leads to some good speed improvements with spatially queries,
however, as features no longer need to be turned into java objects and
processed, the db only returns the ones that filter correctly. It should
work fine, tested against the CITE engine, I only say it's experimental
since it's not nicely detected for you. You have to add a
<usegeos>true</usegeos> to your postgis <DatasourceParams>. Yes, it needs
to be added to every info.xml, we didn't get around to a global
configuration. We figured it would be easier to just do all the
configuration automatically in the next release. Check out
misc/data/featureTypes/rail/info.xml for an example. Please report back
with your experiences with geos, and we'll work on smoother integration
for the next release. If you haven't successfully installed postgis with
geos and you try the usegeos tag you will probably get quite a few
failures for any spatial queries.
Look for 1.1 relatively soon. We may put a beta release out, since
there are quite a few changes. But it should offer solid improvments in
efficiency, robustness, and more data formats, in addition to integrated
WMS.
Email any problems or feature requests to the list, or
geoserver@anonymised.com
Chris