Mike Pumphrey ha scritto:
Hi all. Here is a short summary of the results of running the CITE tests against GeoServer branches/1.6.x (and Geotools 2.4.x) today.
Wow, what a disaster. I've been running the tests myself too and I'm
getting quite different results thought.
To run the tests I've first checked out and built gt2 2.4.x, then built
geoserver, then setup the dbs as necessary and run GeoServer from
within Eclipse, so with Jetty (it's just handier for me).
---
WCS (the "old" engine)
Session 0098: "1.6.4-wcs-1.0.0"
Pass/Fail: 76/21
More information:
http://cite.opengeospatial.org/tsOGC/interface/ViewResultsSummary?ts=0098&sesstype=OGC
Yeah, got a bunch of failures me too due to some breakage in how capability links are getting built:
http://jira.codehaus.org/browse/GEOS-1940
After fixing it I'm down to the usual 6 failures that we know are due
to bugs in the engine instead of bugs in the server itself.
---
WMS 1.1 (the "new" engine)
Session s0058: "1.6.4-wms-1.1"
Everything passed except for:
Test wms:wmsops-getmap-params-format-2 (s0058/w6ac25b3c31d273b1_1):Failed
More information:
http://cite.opengeospatial.org/teamengine/viewSessionLog.jsp?session=s0058
Trying to make the same request as the engine I get:
<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE ServiceExceptionReport SYSTEM "http://schemas.opengis.net/wms/1.1.1/WMS_exception_1_1_1.dtd"> <ServiceExceptionReport version="1.1.1" > <ServiceException code="LayerNotDefined">
Could not find layer cite:Lakes
</ServiceException></ServiceExceptionReport>
But this may due to the fact you reconfigured your geoserver to
work on a different cite test...
Anyway, my test run ended with a full pass for this test.
---
WFS 1.0 (the "new" engine)
Session s0059: "1.6.4-wfs-1.0"
About 50% failure, by my eye
More information
http://cite.opengeospatial.org/teamengine/viewSessionLog.jsp?session=s0059
100% pass for me.
---
WFS 1.1 (the "new" engine)
Session s0060: "1.6.4-wfs-1.1"
I got an error right out of the gate with the wfs:readiness-tests. The log states:
FAILURE: The resulting wfs:FeatureCollection must include at least 4 sf:PrimitiveGeoFeature instances from the test data set.
This is most likely user error, but I couldn't be sure.
In my case, I was able to run the whole test suite, but I got a bunch of
failures in GetFeature tests due to a bug in sorting handling:
http://jira.codehaus.org/browse/GEOS-1939
Gabriel is working on it.
More information:
http://cite.opengeospatial.org/teamengine/viewSessionLog.jsp?session=s0060
Strange, if you look in the detailed report you see the following error message thrown by GeoServer:
Response from parser p:XMLValidatingParser.WFS:
<ows:ExceptionReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ows="http://www.opengis.net/ows"
version="1.0.0"
xsi:schemaLocation="http://www.opengis.net/ows http://geo.openplans.org:8080/geoserver_cite/schemas/ows/1.0.0/owsExceptionReport.xsd">
<ows:Exception exceptionCode="NoApplicableCode">
<ows:ExceptionText>java.lang.RuntimeException: Parsing
failed for typeName: java.lang.RuntimeException:
Parsing failed for null:
java.lang.NoClassDefFoundError:
com/sun/msv/datatype/xsd/XmlNames Parsing failed for
typeName: java.lang.RuntimeException: Parsing failed
for null: java.lang.NoClassDefFoundError:
com/sun/msv/datatype/xsd/XmlNames Parsing failed for
null: java.lang.NoClassDefFoundError:
com/sun/msv/datatype/xsd/XmlNames com/sun/msv/datatype/xsd/XmlNames</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>
It seems you're having troubles with the classpath?
So it seems once http://jira.codehaus.org/browse/GEOS-1939 is fixed
we're good to go... thought it would be nice to pinpoint more
exactly why you're getting extra failures I'm not seeing...
Cheers
Andrea