<div dir="ltr">Thanks! It clarifies well the status and how to use WFS FeatureStore to get featureCollections.<br><br>I will be waiting then for the TimeOut param/exception changes in geotk-client-wfs snapshot, for further tests.<br><br>Many thanks again for your reactive support, it's very much appreciated<br></div><div class="gmail_extra"><br><div class="gmail_quote">2014-12-10 14:59 GMT+01:00 johann sorel <span dir="ltr"><<a href="mailto:johann.sorel@geomatys.com" target="_blank">johann.sorel@geomatys.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
That's right, FeatureCollection is not defined in Geoapi, it is
defined in GeotoolKit only.<br>
<br>
<div>On 10/12/2014 14:57, Emmanuel Blondel
wrote:<br>
</div>
</span><div><div class="h5"><blockquote type="cite">
<div dir="ltr">Thanks, but you confirm that they are only
convenient methods, and that there is no more
"Featurecollection" (or similar) interface at GeoAPI level,
right?<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2014-12-10 13:33 GMT+01:00 johann sorel
<span dir="ltr"><<a href="mailto:johann.sorel@geomatys.com" target="_blank">johann.sorel@geomatys.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> When you have a
FeatureStore you can use the method createSession().<br>
<br>
The Session object has many more convenient methods
including FeatureCollections.<span><font color="#888888"><br>
<br>
Johann Sorel</font></span>
<div>
<div><br>
<br>
<br>
<div>On 10/12/2014 13:27, Emmanuel Blondel wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div> Thanks Martin , it would be great
yes. Let me know if something new appears in
snapshot, i will further test with a geoserver WFS
instance.<br>
<br>
Related to the use of WFS geotk client, i would have
a question about the way how data can be retrieved:<br>
- I see there is a FeatureReader, that acts as
iterator if i'm not wrong.<br>
- However, nothing to get a feature collection
object; looking to GeoAPI in parallel, i've realized
that the GeoAPI is not handling anymore a <font face="Courier New, Courier, monospace">FeatureCollection</font>
interface, which was available in previous (old)
versions of GeoAPI. Apparently i'm very late :-/ !.<br>
I thought we had in GeoAPI a single interface for
representing the data retrieved for a WFS
featureType (what we are actually looking for in our
project), but it seems it belongs to the past, and
the highest representation is the <font face="Courier New, Courier, monospace">Feature</font>.<br>
Do you confirm that?<br>
<br>
Thanks again<br>
Emmanuel<br>
<br>
<div>Le 10/12/2014 09:11, Martin Desruisseaux a
écrit :<br>
</div>
<blockquote type="cite">
<pre>Le 10/12/14 17:05, <a href="mailto:emmanuel.blondel1@gmail.com" target="_blank">emmanuel.blondel1@gmail.com</a> a écrit :
</pre>
<blockquote type="cite">
<pre>Ok for a snapshot, i will argue here on the fact we should use first a snapshot until M3 is available, it shouldn't be a problem.
</pre>
</blockquote>
<pre>Thanks
</pre>
<blockquote type="cite">
<pre>Some questions:
- Is it reasonable to make this timeout hardcoded in geotk? Isn't there a way to specify this timeout threshold as client param..?
</pre>
</blockquote>
<pre>Yes it should be a parameter. I'm not familiar with the way
WFSFeatureStore uses optional parameters. If I find an obvious place
where to put it, I will do. Otherwise a static constant and a "TODO"
note gives an opportunity to revisit this question by someone more
familiar. There is a danger that a "TODO" note is forgot for a long
time, but it should be no longer than until the code is ported to SIS
(since we try to resolve pending issue in this process).
</pre>
<blockquote type="cite">
<pre>- if it is only a time 'warning', ie not an exception, why should i have a null getcapabilities? I would expect a result anyway.
</pre>
</blockquote>
<pre>I agree, this is why I proposed alternatives in my previous email. I
would prefer an exception to be thrown, and Johann seems to agree. Would
it be okay for you?
</pre>
<blockquote type="cite">
<pre> - in case it's'considered as failure, i should have a timeout exception (but it supposes that i can specify the timeout, otherwise it would be very restrictive and will not work for large GetCapabilities docs)
</pre>
</blockquote>
<pre>Yes I agree for the TimeoutException. I will try to find a place for the
timeout parameter.
Martin
</pre>
</blockquote>
<br>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<span>
<pre>_______________________________________________
Geotoolkit mailing list
<a href="mailto:Geotoolkit@lists.osgeo.org" target="_blank">Geotoolkit@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/geotoolkit" target="_blank">http://lists.osgeo.org/mailman/listinfo/geotoolkit</a></pre>
</span></blockquote>
<br>
</div>
<br>
_______________________________________________<br>
Geotoolkit mailing list<br>
<a href="mailto:Geotoolkit@lists.osgeo.org" target="_blank">Geotoolkit@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geotoolkit" target="_blank">http://lists.osgeo.org/mailman/listinfo/geotoolkit</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Geotoolkit mailing list<br>
<a href="mailto:Geotoolkit@lists.osgeo.org">Geotoolkit@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geotoolkit" target="_blank">http://lists.osgeo.org/mailman/listinfo/geotoolkit</a><br></blockquote></div><br></div>