Aweseome, thanks Ryan. So you did manage to get it at least sort of working? Are any of the issues huge blockers? Any priority order in which we should attempt to hit them? Not sure if we'll get to them for a bit, as not many people have been requesting them, but we'll try to some time - error reports like this definitely help us out a ton.
best regards,
Chris
Ryan Hofschneider wrote:
Howdy:
I've been playing with the WFS DataStore in order to support cascaded WFS requests. For anyone wanting to do the same at this stage of development (I've been playing with GeoServer 1.3.1beta), you might want to check these out:
http://jira.codehaus.org/browse/GEOS-629
http://jira.codehaus.org/browse/GEOT-861
http://jira.codehaus.org/browse/GEOT-860
http://jira.codehaus.org/browse/GEOS-628
http://jira.codehaus.org/browse/GEOS-630
http://jira.codehaus.org/browse/GEOS-627
http://jira.codehaus.org/browse/GEOS-626
Cheers,
Ryan
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
On May 30, 2006, at 11:08 AM, Chris Holmes wrote:
So you did manage to get it at least sort of working?
Yup. I have done limited testing and have found that with the referenced changes all the WFS/WFS-T requests work via cascading, with the exception of GetFeatureWithLocks and LockFeature. (This isn't due to a bug, but simply because WFSFeatureStore does not implement the FeatureLocking methods.) The WFS server on the back end was a second instance of GeoServer.
Are any of the issues huge blockers? Any priority order in which we should attempt to hit them?
Required for cascaded GetFeature requests to work at all:
http://jira.codehaus.org/browse/GEOS-628
http://jira.codehaus.org/browse/GEOT-860
http://jira.codehaus.org/browse/GEOS-629
Required for cascaded Transaction requests to work at all:
http://jira.codehaus.org/browse/GEOS-627
Pretty important, but not directly noticeable through casual testing:
http://jira.codehaus.org/browse/GEOS-630
Won't be noticed by most:
http://jira.codehaus.org/browse/GEOS-626
For the last issue:
http://jira.codehaus.org/browse/GEOT-861
I am sure I was able to trigger it through some request, and the code is obviously incorrect, but now I can't seem to get it to execute.
Most of the fixes are only a few lines, though admittedly that is from a "just-get-it-working-for-me" perspective and does not take into account the larger design.
Cheers,
Ryan
Thanks Ryan. I updated the wiki page, feel free to add anything there: http://docs.codehaus.org/display/GEOSDOC/WFS+DataStore
And we'll try to hit the issues soon.
Chris
Ryan Hofschneider wrote:
On May 30, 2006, at 11:08 AM, Chris Holmes wrote:
So you did manage to get it at least sort of working?
Yup. I have done limited testing and have found that with the referenced changes all the WFS/WFS-T requests work via cascading, with the exception of GetFeatureWithLocks and LockFeature. (This isn't due to a bug, but simply because WFSFeatureStore does not implement the FeatureLocking methods.) The WFS server on the back end was a second instance of GeoServer.
Are any of the issues huge blockers? Any priority order in which we should attempt to hit them?
Required for cascaded GetFeature requests to work at all:
http://jira.codehaus.org/browse/GEOS-628
http://jira.codehaus.org/browse/GEOT-860
http://jira.codehaus.org/browse/GEOS-629
Required for cascaded Transaction requests to work at all:
http://jira.codehaus.org/browse/GEOS-627
Pretty important, but not directly noticeable through casual testing:
http://jira.codehaus.org/browse/GEOS-630
Won't be noticed by most:
http://jira.codehaus.org/browse/GEOS-626
For the last issue:
http://jira.codehaus.org/browse/GEOT-861
I am sure I was able to trigger it through some request, and the code is obviously incorrect, but now I can't seem to get it to execute.
Most of the fixes are only a few lines, though admittedly that is from a "just-get-it-working-for-me" perspective and does not take into account the larger design.
Cheers,
Ryan
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org