[geotk] NullPointerException with WFSFeatureStore

[emmanuel.blondel1 at gmail.com]

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.

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..?

- if it is only a time 'warning', ie not an exception, why should i have a null getcapabilities? I would expect a result anyway.
 
- 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)

What do you think?

Emmanuel

------Message d'origine------
De: Martin Desruisseaux
À: emmanuel.blondel1 at gmail.com
À: geotoolkit at lists.osgeo.org
Objet: Re: [geotk] NullPointerException with WFSFeatureStore
Envoyé: 10 déc. 2014 08:08

Le 10/12/14 15:58, emmanuel.blondel1 at gmail.com a écrit :
> Thanks Martin for the feedback, i confirm it's more than possible that this server takes more than 10s, and indeed i got the warning.
Thanks for the confirmation. Johann, would it be reasonable to increase
the timeout delay?

> In case of fixes, can you just tell if it is going to be in a SNAPSHOT only? Or if it is going to be merged to current milestone M2?
It would be in the SNAPSHOT, until we publish a new M3 milestone.
However we have been asked to publish milestones more often (e.g. once
per month). It depends on how easy or difficult it is to depends on an
existing release or milestone of GeoAPI and SIS...

    Martin


---- Envoyé avec BlackBerry® d'Orange ----