> 1) access to version negotiation
>>
>
> I'm with you now on this one. The only thing I want confirmation for: the
> method createGetCapabilitiesRequest doesn't appear to be called from
> anywhere inside the module. Is the idea that udig calls this method
> explicitly, so the version negotiation doesn't happen automatically? If I
> got that right, this has been sorted. I made the same method inside wfs-ng.
It would be extra cool to avoid duplication of logic, if you can provide
another way to access the same information that is fine. I tried letting
the WFSDataStore connect and then asking for the WFS Client - but I could
never find a method to give me access to the final GetCapabilities the
client ended up with.
Admittedly this information should be in the DataStore Info object, so if
you have that working we can remove the createGetCapabilitiesRequest method.
2) Default output format WFS=1.0.0 = GML2, WFS 1.1 = GML3, WFS=2.0 = GML?
>>
> This has been sorted. I actually found there was already a
> straight-forward way in there to give preference to one format over
> another, a way to change the order in which he searches, but it had not
> been configured properly for WFS 1.0.
Good to know, thanks!
3) namespace
>>
>> Namespace should be not only optional, but marked as LEVEL="advanced" (or
>> even LEVEL="program" if it something that geoserver fills in automatically
>> to match the workspace namespace)
>>
> Done.
>
Thanks, what did the right answer end up being? advanced or program...
> Everything has been committed to the branch and is now in the pull request
> as well.
>
> I tested everything in udig and it works splendidly (apart from the
> version negotiation thing, you have to assist me on that one).
>
> Please let me know what else is required to get the module upgraded!
>
As the Aussies say - you are a champion!
I will have a look tomorrow, the real test is editing - but I am not sure
if you implemented that?
Background: Editing is a test of FeatureId
<http://docs.geotools.org/latest/javadocs/org/geotools/filter/identity/FeatureIdImpl.html>
handling, we use a temporary FeatureId during the GeoTools transaction ...
and then during GeoTools transaction commit the WFSDataStore sends a WFS-T
TransactionRequest .. and then parse through the TransactionResponse
document updating each temporary FeatureId with the final identifier
assigned by the server.
For details see FetureIdImpl origionalFid, fid and setFid( String ).
------------------------------------------------------------------------------
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel