Hi,
I’m working on fixing compliance with the WFS 2.0 CITE tests and stubled into something … intersting?
Our WFS 2.0 schemas, output of DescribeFeatureType, claim there are nillable properties:
xsd:complexContent
<xsd:extension base=“gml:AbstractFeatureType”>
xsd:sequence
<xsd:element maxOccurs=“1” minOccurs=“0” name=“multiPointProperty” nillable=“true” type=“gml:MultiPointPropertyType”/>
<xsd:element maxOccurs=“1” minOccurs=“0” name=“multiCurveProperty” nillable=“true” type=“gml:MultiCurvePropertyType”/>
<xsd:element maxOccurs=“1” minOccurs=“0” name=“multiSurfaceProperty” nillable=“true” type=“gml:MultiSurfacePropertyType”/>
<xsd:element maxOccurs=“1” minOccurs=“1” name=“doubleProperty” nillable=“false” type=“xsd:double”/>
<xsd:element maxOccurs=“1” minOccurs=“0” name=“intRangeProperty” nillable=“true” type=“xsd:string”/>
<xsd:element maxOccurs=“1” minOccurs=“1” name=“strProperty” nillable=“false” type=“xsd:string”/>
<xsd:element maxOccurs=“1” minOccurs=“1” name=“featureCode” nillable=“false” type=“xsd:string”/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
and then the CITE tests assumes it can run PropertyIsNil filters on them… which would not even parse, but I have a simple fix for that locally
(see https://osgeo-org.atlassian.net/browse/GEOS-6033 for the report about no support for parsing that).
Now, with the fix the request goes through and then the CITE test fail because they do expect to find an empty element with
xsi:nil=‘true’, while GeoServer’s code does not emit the element at all.
There is also a symmetric ticket open on the write side here:
https://osgeo-org.atlassian.net/browse/GEOS-3126
Wondering, given our current behavior, wouldn’t it be better to not add the nillable attribute in the schema?
The notion that an element might be missing is already present in minOccurs=“0” no?
It seems that if we keep the schema as is today, then we’d have to change the way we encode the GML outputs (to add the element with
nil and eventually nil reason instead of omitting them) and the way we parse inputs for transaction (to handle the same representation in input)
Cheers
Andrea
···
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.