We had many problems using the earlier version of geoserver (RC3 just
released). Many problems related on Tomcat at start (geoserver start)
and, after that, we cannot make a Feature Type reading Post Gis, it
doesn´t appears in the feature type new´s list our layers, any option
of localHost PostGis appears. Is there any new configuration than we
have to do to correctly install new release of geoserver or there are
problems on the last release?
We already have problems reading a large layer (always in post gis)
because some features doesn´t appears reading from Geoserver (simple
getmap request), but those features appears when reading using another
software (UDIG reading directly from postgis) this problem was using
RC2 release.
We had many problems using the earlier version of geoserver (RC3 just
released). Many problems related on Tomcat at start (geoserver start)
and, after that, we cannot make a Feature Type reading Post Gis, it
doesn´t appears in the feature type new´s list our layers, any option
of localHost PostGis appears. Is there any new configuration than we
have to do to correctly install new release of geoserver or there are
problems on the last release?
There are problems on the last release - my bad actually.
We lost the geotools test server (called feathers) some months ago, so PostGIS QA tests have not been run for a while. I have started setting up some new read only tests, and we have connection information for a scratch database we can use for read/write tests.
We have backed out the changes that caused the Feature Type problems, it sounds like there is also a BBox problem for WMS that I have not heard more details about.
Ideas:
1. We can port the PostGisDataStoreAPI test over to fixture.properties (so it will only run against a local postgis install?)
2. PostgisDataStoreTest against geotools-test.fixture
3. Create some kind of PostgisDatqaStoreReadonly test against demo-bc-fixture.properties
Once again if anyone can find the contents that used to be on featheres it will save us rewriting PostgisDataStoreTest.
We already have problems reading a large layer (always in post gis)
because some features doesn´t appears reading from Geoserver (simple
getmap request), but those features appears when reading using another
software (UDIG reading directly from postgis) this problem was using
RC2 release.
UDIG has its own subclass of the PostGIS DataStore, it was my attempt to merge the optimizations back to geotools that created these problems (I should not of even tried without test cases).