[Fdo-trac] [fdo-trac] #998: WFS DescribeSchema fails on landvic service
FDO
trac_fdo at osgeo.org
Fri Sep 30 00:01:31 PDT 2022
#998: WFS DescribeSchema fails on landvic service
--------------------------+------------------------
Reporter: jng | Owner: jng
Type: defect | Status: assigned
Priority: major | Milestone: 4.1.0
Component: WFS Provider | Version: 4.1.0
Severity: 3 | Resolution:
Keywords: | External ID:
--------------------------+------------------------
Comment (by ajinopenspatial):
Hi Jacki,
After debugging the code I found out the real reason of the issue is from
truncating the "Type" or "_Type" from the end of name property of the xml
node "xsd:complexType" to get the layer's class name. If you check the
test.xml file attached on the ticket you could find the 2 names are:
WATER_IRRIGATION_SYSTEM_ALLOCATION_Type and
WATER_IRRIGATION_SYSTEM_ALLOCATIONType. After truncating the "Type" or
"_Type" at the end you will get the same class name
"WATER_IRRIGATION_SYSTEM_ALLOCATION" which caused the 2nd exception while
inserting it twice into a dictionary. After detailed search I found out
that the truncate logic is defined in a .h file named
"SchemaFromExternal.h" sitting under folder "workspace\fdo-trunk-
dbg\Fdo\Unmanaged\Src\Fdo\Schema"(there is another file named
"SchemaFromExternal.xslt" whose content is similar to the head file. but
changing it or not will not affect the build). If we remove the lines
whose line number is from 4090 to 4093 and rebuild the solution then you
could run the unit test successfully to access the url
"https://services.land.vic.gov.au/catalogue/publicproxy/guest/dv_geoserver/datavic/wfs?request=DescribeFeatureType"
My question here is: is there a possibility that the published WFS layer's
complexType name appended with _Type(such as the table name is A then its
complexType name is A_Type)? From our side and the url in this ticket all
names are appended with "Type" only after their table names. If appending
"_Type" will never happen in the real word then removing the lines from
the head file would be safe. Otherwise you may have to design a mechanism
to know which was appended.
--
Ticket URL: <https://trac.osgeo.org/fdo/ticket/998#comment:7>
FDO <http://fdo.osgeo.org/>
Feature Data Objects
More information about the fdo-trac
mailing list