<div dir="ltr"><div>Hi, <br></div><div>I just checked the goals of the work on the WFS provider. It is not a refactor in fat, sorry for having used that word. The work consists in having a closer look to the WFS and snapping cache interactions because they cause lots of problems when the distant database has triggers that would require WFS cache reloading and then snapping cache reloading. <br></div><div>Maybe Vincent can tell more about that, but it's not a major change then. I should'nt have raised the hand here, sorry for the noise. <br></div><div>Regards, <br></div><div>Régis<br></div></div><br><div class="gmail_quote"><div dir="ltr">Le mar. 4 sept. 2018 à 08:51, Jonathan Moules <<a href="mailto:jonathan-lists@lightpear.com">jonathan-lists@lightpear.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>I'd suggest based on Tom's post that the work should include some
sort of reliable way of testing the WFS client (and of course full
test coverage) - I don't know if GeoServer is Docker-happy these
days, but the default install in a VM should be sufficient for the
task (it comes with test layers) - although GeoServer doesn't
support WFS-T for writing.<br>
</p>
Cheers,<br>
Jonathan<br>
<br>
<div class="m_9071611927226938488moz-cite-prefix">On 03/09/2018 12:04, Régis Haubourg
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi all, <br>
</div>
<div>I very much think that the WFS client is an really bad
state, and is not really reliable, especially in WFS-T
context. <br>
</div>
<div>The good news is that we just have been funded to refactor
it ! <br>
</div>
<div>The work should start in september and land in 3.6. I will
let our dev's come here with more technical details about the
goals. I hope we will also be able to take benefit of this to
this the OGC compliancy of the client here. <br>
</div>
<div>Best regards, <br>
</div>
<div>Régis<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">Le lun. 3 sept. 2018 à 11:36, Tom Chadwin <<a href="mailto:tom.chadwin@nnpa.org.uk" target="_blank">tom.chadwin@nnpa.org.uk</a>>
a écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I can't
offer any helpful suggestions, but just to let you know I
finally had<br>
to disable all my plugin WFS tests. I used to cope, by
rerunning failed<br>
Travis runs, but by about three months ago, it seemed no
longer usable -<br>
failure after failure.<br>
<br>
I was using a third-party WFS, and perhaps I could have got
round this by<br>
adding a WFS provider to the test docker image, but in this
plugin's case, I<br>
didn't think it worth the significant effort to do so. The
WM(T)S tests also<br>
use third-party sources and seem stable, so perhaps this
wasn't the<br>
underlying issue anyway.<br>
<br>
If an improvement or solution could be found, it would be
great to reinstate<br>
these tests.<br>
<br>
Thanks<br>
<br>
Tom<br>
<br>
<br>
<br>
-----<br>
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon <br>
--<br>
Sent from: <a href="http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html" rel="noreferrer" target="_blank">http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html</a><br>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></blockquote>
</div>
<br>
<fieldset class="m_9071611927226938488mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
QGIS-Developer mailing list
<a class="m_9071611927226938488moz-txt-link-abbreviated" href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a>
List info: <a class="m_9071611927226938488moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a class="m_9071611927226938488moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></blockquote></div>