On Thu, May 1, 2014 at 2:50 PM, Justin Deoliveira <jdeol...@boundlessgeo.com
> wrote:
> Thanks for helping out with this Andrea.
>
> The xerces dependency from Jetty makes sense. And I guess this one just
> laid dormant while we ran on java 6. Perhaps the switch did trigger
> something.
>
> Anyways, I think it's worth a shot to try removing it.
>
Done that, we're doing to a single failure:
[exec] Test wfs:wfs-main (wfs-1.1.0) Failed (Inherited Failure)
[exec] Test wfs:readiness-tests (wfs-1.1.0/d41e34700_1) Failed
(Inherited Failure)
[exec] Test wfs:basic-main
(wfs-1.1.0/d41e34700_1/d41e749_1) Failed (Inherited Failure)
[exec] Test wfs:run-GetFeature-POST
(wfs-1.1.0/d41e34700_1/d41e749_1/d41e24772_1) Failed (Inherited
Failure)
[exec] Test wfs:wfs-1.1.0-Basic-GetFeature-tc5.3
(wfs-1.1.0/d41e34700_1/d41e749_1/d41e24772_1/d41e15477_1) Failed
(Inherited Failure)
[exec] Test ctl:assert-xpath
(wfs-1.1.0/d41e34700_1/d41e749_1/d41e24772_1/d41e15477_1/d41e16520_1)
Failed
[exec] Test ctl:assert-xpath
(wfs-1.1.0/d41e34700_1/d41e749_1/d41e24772_1/d41e15477_1/d41e16530_1)
Failed
However... I cannot reproduce this one locally, not sure what might be
causing it. The logs are not that useful:
[exec] Testing wfs:wfs-1.1.0-Basic-GetFeature-tc5.3
(wfs-1.1.0/d41e34700_1/d41e749_1/d41e24772_1/d41e15477_1)...
[exec] Assertion: The response entity must be
schema valid and include any optional feature properties requested by
the client. The document element must be a wfs:FeatureCollection.
[exec] Testing ctl:assert-xpath
(wfs-1.1.0/d41e34700_1/d41e749_1/d41e24772_1/d41e15477_1/d41e16520_1)...
[exec] Assertion:
[exec] Evaluates the given XPath expression against the
input document and
[exec] returns a boolean result according to the XPath
specification (see
[exec] http://www.w3.org/TR/xpath#section-Boolean-Functions).
[exec]
[exec] The expression
'//wfs:FeatureCollection' is false.
[exec] Test ctl:assert-xpath Failed
[exec] Testing ctl:assert-xpath
(wfs-1.1.0/d41e34700_1/d41e749_1/d41e24772_1/d41e15477_1/d41e16530_1)...
[exec] Assertion:
[exec] Evaluates the given XPath expression against the
input document and
[exec] returns a boolean result according to the XPath
specification (see
[exec] http://www.w3.org/TR/xpath#section-Boolean-Functions).
[exec]
[exec] The expression '//sf:measurand' is false.
[exec] Test ctl:assert-xpath Failed
[exec] Testing ctl:assert-xpath
(wfs-1.1.0/d41e34700_1/d41e749_1/d41e24772_1/d41e15477_1/d41e16541_1)...
[exec] Assertion:
[exec] Evaluates the given XPath expression against the
input document and
[exec] returns a boolean result according to the XPath
specification (see
[exec] http://www.w3.org/TR/xpath#section-Boolean-Functions).
[exec]
[exec] Test ctl:assert-xpath Passed
[exec] Test wfs:wfs-1.1.0-Basic-GetFeature-tc5.3
Failed (Inherited failure)
>From what I can see, GeoServer is not returning a feature collection when
that request is run, when running locally (where it
works) the logs from the CITE engine web UI look like:
<wfs:GetFeature xmlns="http://www.occamlab.com/ctl";
xmlns:ctl="http://www.occamlab.com/ctl";
xmlns:gml="http://www.opengis.net/gml";
xmlns:myparsers="http://teamengine.sourceforge.net/parsers";
xmlns:ogc="http://www.opengis.net/ogc";
xmlns:ows="http://www.opengis.net/ows";
xmlns:p="http://teamengine.sourceforge.net/parsers";
xmlns:parsers="http://www.occamlab.com/te/parsers";
xmlns:saxon="http://saxon.sf.net/";
xmlns:sf="http://cite.opengeospatial.org/gmlsf";
xmlns:te="http://www.occamlab.com/te";
xmlns:tec="java:com.occamlab.te.TECore"
xmlns:tems="java:com.occamlab.te.web.MonitorServlet"
xmlns:wfs="http://www.opengis.net/wfs";
xmlns:xi="http://www.w3.org/2001/XInclude";
xmlns:xlink="http://www.w3.org/1999/xlink";
xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
service="WFS"
version="1.1.0">
<wfs:Query srsName="urn:ogc:def:crs:EPSG::4326"
typeName="sf:PrimitiveGeoFeature">
<ogc:Filter>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>sf:intProperty</ogc:PropertyName>
<ogc:Literal>300</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Filter>
</wfs:Query>
</wfs:GetFeature>
Response from parser p:XMLValidatingParser.GMLSF1:
<wfs:FeatureCollection xmlns:gml="http://www.opengis.net/gml";
xmlns:it.geosolutions="http://www.geo-solutions.it";
xmlns:ogc="http://www.opengis.net/ogc";
xmlns:ows="http://www.opengis.net/ows";
xmlns:sf="http://cite.opengeospatial.org/gmlsf";
xmlns:wfs="http://www.opengis.net/wfs";
xmlns:xlink="http://www.w3.org/1999/xlink";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
numberOfFeatures="1"
timeStamp="2014-05-01T08:50:15.799Z"
xsi:schemaLocation="http://cite.opengeospatial.org/gmlsf
http://localhost:8080/geoserver/wfs?service=WFS&version=1.1.0&request=DescribeFeatureType&typeName=sf%3APrimitiveGeoFeature
http://www.opengis.net/wfs
http://localhost:8080/geoserver/schemas/wfs/1.1.0/wfs.xsd";>
<gml:boundedBy>
<gml:Envelope srsName="urn:ogc:def:crs:EPSG::4326">
<gml:lowerCorner>45.174 30.466</gml:lowerCorner>
<gml:upperCorner>45.891 30.899</gml:upperCorner>
</gml:Envelope>
</gml:boundedBy>
<gml:featureMembers>
<sf:PrimitiveGeoFeature gml:id="PrimitiveGeoFeature.f008">
<gml:description>description-f008</gml:description>
<gml:name>name-f008</gml:name>
<gml:boundedBy>
<gml:Envelope srsName="urn:ogc:def:crs:EPSG::4326">
<gml:lowerCorner>45.174 30.466</gml:lowerCorner>
<gml:upperCorner>45.891 30.899</gml:upperCorner>
</gml:Envelope>
</gml:boundedBy>
<sf:surfaceProperty>
<gml:Polygon srsName="urn:ogc:def:crs:EPSG::4326">
<gml:exterior>
<gml:LinearRing>
<gml:posList>45.174 30.899 45.652 30.466 45.891
30.466 45.174 30.899</gml:posList>
</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
</sf:surfaceProperty>
<sf:intProperty>300</sf:intProperty>
<sf:measurand>783.5</sf:measurand>
<sf:dateTimeProperty>2006-06-28T05:08:00Z</sf:dateTimeProperty>
<sf:dateProperty>2006-12-12Z</sf:dateProperty>
<sf:decimalProperty>18.92</sf:decimalProperty>
</sf:PrimitiveGeoFeature>
</gml:featureMembers>
What can make a simple equality test ("intProperty" = 300) fail on the
build server? And why only this one.
We should probably run the test again and see in the GeoServer logs, maybe
we'll find an exception in there.
Time out for me, maybe I'll have a look again during the weekend.
Cheers
Andrea
--
==
Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK
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
-------------------------------------------------------
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
