[CITE-Forum] New beta release

Sebastian Goerke goerke at lat-lon.de
Fri Jul 12 05:43:47 EDT 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I observed the same (already reported to Luis and Richard)

Best Regards

Sebastian

- -- 
l a t / l o n  GmbH
Aennchenstrasse 19               53177 Bonn, Germany
phone ++49 +228 18496-0          fax ++49 +228 18496-29
http://www.lat-lon.de            http://www.deegree.org

Am 12.07.2013 11:29, schrieb Mats Olsson:
> Hello!
> 
> 
> 
> Unfortunately the WFS 2.0 tests don't seem to work at all anymore
> on the beta site. Every single test that runs returns a
> null-pointer exception.
> 
> 
> 
> I retested everything else after the redeployment yesterday and all
> the erroneous inherited failures are gone now.
> 
> 
> 
> The other issues with the other interfaces are still there.
> 
> 
> 
> Best regards,
> 
> Mats Olsson
> 
> Carmenta AB
> 
> 
> 
> 
> 
> *From:*Richard Martell [mailto:rmartell at galdosinc.com] *Sent:* den
> 11 juli 2013 17:26 *To:* Mats Olsson; Luis Bermudez;
> cite-forum at lists.opengeospatial.org; CITE SC *Subject:* RE:
> [CITE-Forum] New beta release
> 
> 
> 
> Hi Matts,
> 
> 
> 
> A fix for CITE-785 (WFS 2.0 DateTime parsing problem) was
> committed yesterday. Resolving it turned out to require
> 
> adding constructor functions to the XPath expression for the
> (simple) property type as determined from the property
> 
> declaration in the app schema.
> 
> 
> 
> e.g.
> 
> xs:dateTime(ns1:dateTimeProperty) ge
> xs:dateTime('2006-06-28T11:08:00.000Z')
> 
> 
> 
> I?m working on the remaining WFS2 issues this week.
> 
> 
> 
> --
> 
> Richard
> 
> 
> 
> 
> 
> *From:*CITE-Forum 
> [mailto:cite-forum-bounces+rmartell=galdosinc.com at lists.opengeospatial.org]
>
> 
*On Behalf Of *Mats Olsson
> *Sent:* Thursday, 11 July, 2013 05:11 *To:* Luis Bermudez;
> cite-forum at lists.opengeospatial.org 
> <mailto:cite-forum at lists.opengeospatial.org>; CITE SC *Subject:*
> Re: [CITE-Forum] New beta release
> 
> 
> 
> Hello!
> 
> 
> 
> Thought I should provide some general feedback on the latest TEAM
> Engine beta.
> 
> 
> 
> I have tried several of the tests and there still seems to be a
> number of issues with them.
> 
> 
> 
> To avoid spamming the mailing list too much I have summarized
> everything I found in a single email where I think there might be
> an issue with the tests.
> 
> 
> 
> I'll try to get everything that is not already reported into the
> issue tracker as well.
> 
> 
> 
> WMS 1.1.1
> 
> 
> 
> 1. The tests sends a weird SRS parameter in a couple of request: 
> SRS=EPSG:4326+EPSG:4326. This only happens if the layer has a 
> boundingbox declared for the requested layer in the capabilities 
> document. All our layers also have multiple SRS-tags including one
> for EPSG:4326.
> 
> Probably related to a similar problem in WMS 1.3.0 with Issue
> Tracker ID 783.
> 
> 
> 
> Applies to:
> 
> Test wms:wmsops-getmap-each-layer
> 
> Test wms:wmsops-getmap-layer-encoded-name
> 
> 
> 
> WMS 1.3.0
> 
> 
> 
> The issue reportedEvery single test that runs returns a
> null-pointer exception.



I retested everything else after the redeployment yesterday and all
the erroneous inherited failures are gone now.

  in Issue Tracker ID 783 seems to work for me now (but
> note that the similar problem in WMS 1.1.1 is still there).
> 
> 
> 
> 1. Test getcapabilities:ex_geobbox-coordinates -  This test don't
> seem to handle negative coordinates very well, it fails for layers
> where eastBoundLongitude or northBoundLatitude (and possibly also
> maxx or maxy in any BoundingBox?) in a EX_GeographicBoundingBox are
> negative. In our configuration these layers are DividedRoutes,
> Lakes & Ponds.
> 
> 
> 
> WCS 1.1.1
> 
> 
> 
> 1. There are some XPath problems in the tests when using multiple 
> Boundingboxes in the same Coverage, these generate two types of
> errors:
> 
> Cannot convert string "4150496.42888048 1117 1396" to xs:decimal
> (This is some sort of concatenation of UpperCorner for both
> boundingboxes used in this coverage).
> 
> or
> 
> Arithmetic operator is not defined for arguments of types
> (xs:string, xs:string)
> 
> 
> 
> Applies to all GetCoverage tests that return anything other than 
> ExceptionReports.
> 
> 
> 
> Previously reported as part of Issue Tracker ID 782.
> 
> 
> 
> WFS 1.1.0
> 
> 
> 
> Everything seems to work in these tests.
> 
> 
> 
> WFS 2.0.0
> 
> 
> 
> 1. Regression(?) since previous beta: About 1/3 of all tests in the
> WFS 2.0 test suite now generate an java.lang.RuntimeException: 
> java.lang.NullPointerException error.
> 
> They do not appear to send any actual requests sent so I suspect
> there is a problem with parsing the capabilities document. I will
> look further into this and see if a can come up with a more
> specific description of what goes wrong.
> 
> 
> 
> 2. Test which uses the DateTime parsing (ID 785 in the Issue
> tracker) doesn?t run at all anymore so I am unable to test if the
> DateTime parsing problem has been fixed.
> 
> 
> 
> WMTS 1.0.0
> 
> 
> 
> "Execute this test again" do not work anywhere, it does not seem to
> do anything. This means you will have to create a new session every
> time you want to retest and run the entire session which is very
> time-consuming.
> 
> 
> 
> It is very difficult to see what prerequisite failed for many of
> the tests that are skipped. In future version perhaps it would be
> worth considering adding a description of what prerequisite failed
> to make it easier to find. Every single test that runs returns a
> null-pointer exception.



I retested everything else after the redeployment yesterday and all
the erroneous inherited failures are gone now.


> 
> 
> 1. UpdateSequence is a string, but the test 
> wmts:Server.KVP.GET.GetCapabilities.Request.UpdateSequence try to 
> compare it with a double.
> 
> 
> 
> Error in call to extension function {public java.lang.Object 
> com.occamlab.te.TECore.callFunction(net.sf.saxon.expr.XPathContext,java.lang.String,java.lang.String,net.sf.saxon.om.NodeInfo)
>
> 
throws java.lang.Exception}: Exception in extension function
> java.lang.Exception: Fatal Error: Cannot compare xs:double to
> xs:string; SystemID: 
> file:/srv/local/teamengine/work/srv_local_teamengine_scripts_wmts_1.0.0_ctl_/owsFunctions/owsFunctions$KVP.GetCapabilities.Request.UpdateSequence.fn;
>
> 
Line#: 69; Column#: -1
> 
> Fatal Error: Cannot compare xs:double to xs:string; SystemID: 
> file:/srv/local/teamengine/work/srv_local_teamengine_scripts_wmts_1.0.0_ctl_/owsFunctions/owsFunctions$KVP.GetCapabilities.Request.UpdateSequence.fn;
>
> 
Line#: 69; Column#: -1
> 
> Failed to compile stylesheet. 2 errors detected.
> 
> Result: Failed
> 
> 
> 
> WPS 1.0.0
> 
> 
> 
> These tests still have the inherited failure when all subtest pass
> issue.
> 
> 
> 
> 1. Issue ID 789, where the tests seem to assume that all ID's have
> to be URNs, I'm not sure that if that is really correct or not.
> 
> 
> 
> 2. Issue ID 790, the "InvalidRequest" exception expected in test 
> wps:general-WPS.General-InvalidRequest. It does not seem to
> mentioned anywhere in the standard.
> 
> 
> 
> CSW 2.0.2
> 
> 
> 
> Still seems to have the inherited failure when all subtest pass
> issue, otherwise works ok.
> 
> 
> 
> best regards,
> 
> Mats Olsson
> 
> Carmenta AB
> 
> 
> 
> *From:*CITE-Forum 
> [mailto:cite-forum-bounces+mats.olsson=carmenta.com at lists.opengeospatial.org]
>
> 
*On Behalf Of *Luis Bermudez
> *Sent:* den 5 juli 2013 17:56 *To:*
> cite-forum at lists.opengeospatial.org 
> <mailto:cite-forum at lists.opengeospatial.org>; CITE SC *Subject:*
> [CITE-Forum] New beta release
> 
> 
> 
> All.
> 
> 
> 
> There is a new beta release with the latest fixes:
> 
> 
> 
> http://cite.opengeospatial.org/te2/
> 
> 
> 
> 
> 
> This release incorporates CTL test suites from r5604 (2013-07-04).
> 
> 
> .
> 
> The following test suites have been updated since the 4.0-rc
> release (2013-05-30):
> 
> 
> 
> * wfs-1.0.0-r6
> 
> * wfs-2.0-r4
> 
> * wmts-1.0-r2 Every single test that runs returns a null-pointer
> exception.



I retested everything else after the redeployment yesterday and all
the erroneous inherited failures are gone now.


> * csw-2.0.2-r7
> 
> * sos-1.0-r7
> 
> * gml-3.2.1-r4
> 
> 
> 
> TEAM Engine is pretty stable at this point. The production site
> will be updated in the coming weeks with the new TEAM Engine,
> incorporating the minor fixes of already approved tests. The tests
> in beta will go for vote in the next weeks/months and will be
> incorporated to the official web site as soon as the tests are
> approved.
> 
> 
> 
> As always please let us know if you have any suggestions or
> encounter any issues.
> 
> 
> 
> Best Regards,
> 
> 
> 
> Luis
> 
> -------------
> 
> Luis Bermudez
> 
> lbermudez at opengeospatial.org <mailto:lbermudez at opengeospatial.org>
> 
> 
> 
> 
> The OGC: Making Location Count...
> 
> http://www.opengeospatial.org/contact
> 
> 
> 
> _______________________________________________ CITE-Forum mailing
> list CITE-Forum at lists.opengeospatial.org 
> https://lists.opengeospatial.org/mailman/listinfo/cite-forum
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlHfz9IACgkQq1hDh4aJykJYKQCfR5KvABrvcM0o0T7SW1jKVooa
c/4AoLbtQ85abicjzbeEfJ4JG5WorMDX
=ifRf
-----END PGP SIGNATURE-----


More information about the CITE-Forum mailing list