Paul,
I saw your recent comment on GEOS-1283. There has been no further
resolution on this issue, because we can't replicate it.
Have you tried a recent nightly geoserver build? A "latest" 1.6.x-series
build from here:
http://traffic.openplans.org/geoserver/trunk/
You'll also need to follow the instructions here, to get the arcsde
extension working in the nightly build:
http://www.nabble.com/Re%3A-Error-creating-ArcSDE-FeatureType-p13235169.html
If the problem is still present, then let us know and we can try and do
further diagnostics. Probably at that point, the easiest solution would be
to try and get a direct connection to your ArcSDE server and see what's
going wrong! Alternatively, perhaps you could create a shapefile of some of
the sample data and we could try and replicate the problem on our end?
Good luck,
--saul
--
View this message in context: http://www.nabble.com/GEOS-1283-tf4681549.html#a13377613
Sent from the GeoServer - Dev mailing list archive at Nabble.com.
Hi Saul, Paul,
sorry I just noticed the issue.
Actually it makes sense if the error happens on geoserver 1.5.x but not on
1.6.x.
Rationale is that exact bug showed up on geotools 2.3.x (used by geoserver
1.5.x) due to the way fids were being handled. At geotools 2.4.x (used by
geoserver 1.6.x), the arcsde plugin got a bunch of improvements from the
complex-features branch, the one that gets rid of this bug being the
introduction of FIDReader, a strategy object to handle feature id fetching.
Could you try and confirm the bug does not show up in 1.6.x for you?
Cheers,
Gabriel
On Wednesday 24 October 2007 04:00:22 am sfarber wrote:
Paul,
I saw your recent comment on GEOS-1283. There has been no further
resolution on this issue, because we can't replicate it.
Have you tried a recent nightly geoserver build? A "latest" 1.6.x-series
build from here:
http://traffic.openplans.org/geoserver/trunk/
You'll also need to follow the instructions here, to get the arcsde
extension working in the nightly build:
http://www.nabble.com/Re%3A-Error-creating-ArcSDE-FeatureType-p13235169.htm
l
If the problem is still present, then let us know and we can try and do
further diagnostics. Probably at that point, the easiest solution would be
to try and get a direct connection to your ArcSDE server and see what's
going wrong! Alternatively, perhaps you could create a shapefile of some
of the sample data and we could try and replicate the problem on our end?
Good luck,
--saul
Hi Saul, Gabriel,
I now have geoserver 1.6.x running (downloaded latest build around 23rd Oct)
and I can confirm that the problem has gone away.
For the sake of completeness I should say that a concurrent upgrade of SDE
to SP3 unfortunately occured during my switch from 1.5.3 to 1.6.x making it
impossible to say what the real solution was.
Many thanks for your help.
Best regards
Paul
Gabriel Roldán-4 wrote:
Hi Saul, Paul,
sorry I just noticed the issue.
Actually it makes sense if the error happens on geoserver 1.5.x but not on
1.6.x.
Rationale is that exact bug showed up on geotools 2.3.x (used by geoserver
1.5.x) due to the way fids were being handled. At geotools 2.4.x (used by
geoserver 1.6.x), the arcsde plugin got a bunch of improvements from the
complex-features branch, the one that gets rid of this bug being the
introduction of FIDReader, a strategy object to handle feature id
fetching.
Could you try and confirm the bug does not show up in 1.6.x for you?
Cheers,
Gabriel
On Wednesday 24 October 2007 04:00:22 am sfarber wrote:
Paul,
I saw your recent comment on GEOS-1283. There has been no further
resolution on this issue, because we can't replicate it.
Have you tried a recent nightly geoserver build? A "latest" 1.6.x-series
build from here:
http://traffic.openplans.org/geoserver/trunk/
You'll also need to follow the instructions here, to get the arcsde
extension working in the nightly build:
http://www.nabble.com/Re%3A-Error-creating-ArcSDE-FeatureType-p13235169.htm
l
If the problem is still present, then let us know and we can try and do
further diagnostics. Probably at that point, the easiest solution would
be
to try and get a direct connection to your ArcSDE server and see what's
going wrong! Alternatively, perhaps you could create a shapefile of some
of the sample data and we could try and replicate the problem on our end?
Good luck,
--saul
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
View this message in context: http://www.nabble.com/GEOS-1283-tf4681549.html#a13420458
Sent from the GeoServer - Dev mailing list archive at Nabble.com.