On Tue, Jun 17, 2014 at 10:54 PM, Bessette-Halsema, Dominique E <
dominique.besse...@gdit.com> wrote:

>  Thanks for the reply.  We recently upgraded from geoserver 2.2.4 to 2.5
> and noticed that the custom delegates are registered differently, and ours
> was not getting picked up.  Is there any other changes to custom delegates
> you know about?  We are looking into it.
>

Hmm... I did not even think that in 2.2.x the delegates were pluggable
already... but I may be wrong. Yes, several changes occurred as WCS 2.0 was
introduced,
but I don't remember exactly what, it all happened several months ago (git
diff/git log are your friend).


>
>
> Also do you know if the WFS getFeature call was modified for the time
> domain?  We are seeing issues for this too, although it may be on our end.
>
>
>
> 18:56:24,256 WARN
> [mil.navy.fnmoc.gis.doc.dataordering.retrieval.RetrieverRunner]
> (pool-28-thread-1) Exception encountered while running retriever; will
> retry the item later.: java.io.IOException: Bad HTTP response: url=
> https://imetoc.nps.edu/geoserver/wfs?service=WFS&version=1.0.0&request=GetFeature&typeName=gis:amdars&cql_filter=BBOX(location,-180.0,-90.0,-157.5,90.0,'EPSG:4326')
> AND uploadtime DURING
> 2014-06-17T19:05:02Z/2014-06-17T18:46:13Z&outputFormat=json, code='200',
> msg='OK', type=text/xml;charset="UTF-8", response='<?xml version="1.0" ?>
>
> <ServiceExceptionReport
>
>    version="1.2.0"
>
>    xmlns="http://www.opengis.net/ogc";
>
>    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
>    xsi:schemaLocation="http://www.opengis.net/ogc
> http://schemas.opengis.net/wfs/1.0.0/OGC-exception.xsd
> <http://www.opengis.net/ogc%20http:/schemas.opengis.net/wfs/1.0.0/OGC-exception.xsd>
> ">
>
>    <ServiceException>
>
>       java.lang.IllegalArgumentException: The temporal position of the
> beginning of the period must be less than (i.e. earlier than) the temporal
> position of the end of the period
>
> The temporal position of the beginning of the period must be less than
> (i.e. earlier than) the temporal position of the end of the period
>

Looks like more correct validation of inputs, look:
2014-06-17T19:05:02Z/2014-06-17T18:46:13Z
The interval is invalid, the begin time is more recent than the end one

Cheers
Andrea

-- 
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to