DescribeFeatureType fails twelve CITE WFS 1.0 tests
---------------------------------------------------
Key: GEOS-2809
URL: http://jira.codehaus.org/browse/GEOS-2809
Project: GeoServer
Issue Type: Bug
Components: WFS
Reporter: Ben Caradoc-Davies
Assignee: Andrea Aime
Attachments: log.xml
GeoServer trunk using web2 and the wfs-1.0 config fails twelve CITE WFS 1.0 tests.
(nabble not responding, so here is the discussion)
-------- Original Message --------
Subject: [ExternalEmail] [Geoserver-devel] CITE wfs-1.0.0 failures for DescribeFeatureType
Date: Tue, 31 Mar 2009 12:15:09 +0800
From: Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
To: Justin Deoliveira <jdeolive@anonymised.com>
CC: Geoserver-devel <geoserver-devel@lists.sourceforge.net>
References: <49CC53B3.7060808@anonymised.com> <49CC6B5C.30603@anonymised.com> <49D039C7.6030006@anonymised.com> <49D088B6.60506@anonymised.com> <49D08D72.8040906@anonymised.com> <49D09180.4060704@anonymised.com>
Ben Caradoc-Davies wrote:
Most tests passed, but something failed. This is on a clean GeoTools
r32719 / GeoServer r11894 checkout, testing web2, *before* my GEOS-2753
patch is applied. The failure was:
Test wfs:main Failed (Inherited Failure)
Justin,
I have 12 failures running CITE wfs-1.0.0 on unmodified geoserver trunk.
I have attached the log for the first of these. I do not know what is
wrong. I built the test engine with Java 5, but am running it with 6.
Can anyone confirm these failures? (This is my first CITE run.)
Kind regards,
Ben.
>log.bat wfs 1.0.0 | perl -ne "print if /Failed/"
Test wfs:main (wfs-1.0.0) Failed (Inherited Failure)
Test wfs:test1.0.0-basic-describefeaturetype-get-1
(wfs-1.0.0/w28aac25b3b9d169b1_1) Failed
Test wfs:test1.0.0-basic-describefeaturetype-get-2
(wfs-1.0.0/w28aac25b3b9d171b1_1) Failed
Test wfs:test1.0.0-basic-describefeaturetype-get-4
(wfs-1.0.0/w28aac25b3b9d175b1_1) Failed
Test wfs:test1.0.0-basic-describefeaturetype-get-5
(wfs-1.0.0/w28aac25b3b9d177b1_1) Failed
Test wfs:test1.0.0-basic-describefeaturetype-get-6
(wfs-1.0.0/w28aac25b3b9d179b1_1) Failed
Test wfs:test1.0.0-basic-describefeaturetype-get-7
(wfs-1.0.0/w28aac25b3b9d181b1_1) Failed
Test wfs:test1.0.0-basic-describefeaturetype-post-1
(wfs-1.0.0/w28aac25b3b9d187b1_1) Failed
Test wfs:test1.0.0-basic-describefeaturetype-post-2
(wfs-1.0.0/w28aac25b3b9d189b1_1) Failed
Test wfs:test1.0.0-basic-describefeaturetype-post-4
(wfs-1.0.0/w28aac25b3b9d193b1_1) Failed
Test wfs:test1.0.0-basic-describefeaturetype-post-5
(wfs-1.0.0/w28aac25b3b9d195b1_1) Failed
Test wfs:test1.0.0-basic-describefeaturetype-post-6
(wfs-1.0.0/w28aac25b3b9d197b1_1) Failed
Test wfs:test1.0.0-basic-describefeaturetype-post-7
(wfs-1.0.0/w28aac25b3b9d199b1_1) Failed
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
-------- Original Message --------
Subject: [ExternalEmail] Re: [Geoserver-devel] CITE wfs-1.0.0 failures for DescribeFeatureType
Date: Tue, 31 Mar 2009 14:04:57 +0800
From: Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
To: Jody Garnett <jody.garnett@anonymised.com>
CC: Geoserver-devel <geoserver-devel@lists.sourceforge.net>, Justin Deoliveira <jdeolive@anonymised.com>
References: <49CC53B3.7060808@anonymised.com> <49CC6B5C.30603@anonymised.com> <49D039C7.6030006@anonymised.com> <49D088B6.60506@anonymised.com> <49D08D72.8040906@anonymised.com> <49D09180.4060704@anonymised.com> <49D198CD.8050605@anonymised.com> <f14fd02c0903302144q6bf9015fwc71c5ff4e3eb2cfb@anonymised.com> <49D1A50C.90902@anonymised.com> <f14fd02c0903302245yf3223epcdd38701d95c51ec@anonymised.com>
Jody Garnett wrote:
Have a look at the log.xml your provided; now I could be reading it
wrong; but it looks like the param value for
VAR_WFS_DESCRIBE_FEATURE_TYPE_HTTP_GET_URL is wrong. Have a look and
let me know what you think.
The URL is http://localhost:8080/geoserver/wfs?request=DescribeFeatureType
This looks OK to me, except that it has no typename, nor is one present
in the list of parameters in the the cite log request section.
If I submit a URL with a typename:
http://localhost:8080/geoserver/wfs?service=WFS&request=DescribeFeatureType&version=1.0.0&typeName=cdf:Fifteen
I get an XML Schema response that includes
<xs:complexType name="Fifteen_Type">
...
and
<xs:element name="Fifteen" type="cdf:FifteenType"
substitutionGroup="gml:_Feature"/>
If I omit the typename parameter and submit the following URL in my web
browser:
http://localhost:8080/geoserver/wfs?service=WFS&request=DescribeFeatureType&version=1.0.0
I get a response that is an XML Schema that has only imports and no
other content. I think this is what the cite tests are complaining about.
What is the expected behaviour of a WFS in response to a
DescribeFeatureType with no TypeName?
I think this should point to your server from the perspective of the
CITE test engine. Are you running CITE locally? I see the file =
"C:\Projects\car605\geoserver\cite\cite\tests\wfs\1.0.0\ets\ctl\wfs.xml"
mentioned so perhaps you are running it locally.
Yes, I am running GeoServer locally.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
-------- Original Message --------
Subject: Re: [Geoserver-devel] [ExternalEmail] Re: CITE wfs-1.0.0 failures for DescribeFeatureType
Date: Tue, 31 Mar 2009 14:22:46 +0800
From: Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
To: Jody Garnett <jody.garnett@anonymised.com>
CC: Geoserver-devel <geoserver-devel@lists.sourceforge.net>, Justin Deoliveira <jdeolive@anonymised.com>
References: <49CC53B3.7060808@anonymised.com> <49CC6B5C.30603@anonymised.com> <49D039C7.6030006@anonymised.com> <49D088B6.60506@anonymised.com> <49D08D72.8040906@anonymised.com> <49D09180.4060704@anonymised.com> <49D198CD.8050605@anonymised.com> <f14fd02c0903302144q6bf9015fwc71c5ff4e3eb2cfb@anonymised.com> <49D1A50C.90902@anonymised.com> <f14fd02c0903302245yf3223epcdd38701d95c51ec@anonymised.com> <49D1B289.5070103@anonymised.com>
Ben Caradoc-Davies wrote:
What is the expected behaviour of a WFS in response to a
DescribeFeatureType with no TypeName?
To answer my own question, both the 1.0 and 1.1 specs state that all
feature types should be described if the element DescribeFeatureType is
empty, which implies that no TypeName means describe all feature types.
Looking at, for example, GeoServer 1.5.4, DescribeFeatureType for
multiple feature types is implemented with a single XSD with one import
for each type name.
In GeoServer trunk (CITE wfs 1.0.0):
http://localhost:8080/geoserver/wfs?request=DescribeFeatureType&service=wfs&version=1.0.0
returns these two imports (note bogus typeName):
<xs:import namespace="http://www.opengis.net/cite/data"
schemaLocation="http://localhost:8080/geoserver/wfs?request=DescribeFeatureType&service=wfs&version=1.0.0&typeName"/>
<xs:import namespace="http://www.opengis.net/cite/geometry"
schemaLocation="http://localhost:8080/geoserver/wfs?request=DescribeFeatureType&service=wfs&version=1.0.0&typeName"/>
and because there are no types named in the typename, schema resolution
recurses ad infinitum!
Looks like a bug to me.
Kind regards,
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira