id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
824	behaviour of DUMP TRUE in WFS interface	bartvde@…	mapserverbugs	"{{{
If I have a layer in my MAP file which does not have DUMP TRUE, the layer ends
up in the WFS capabilities. When a GetFeature request is performed, the
following result is retrieved:

<?xml version='1.0' encoding=""ISO-8859-1"" ?>
<wfs:FeatureCollection
   xmlns=""http://www.ttt.org/myns""
   xmlns:myns=""http://www.ttt.org/myns""
   xmlns:wfs=""http://www.opengis.net/wfs""
   xmlns:gml=""http://www.opengis.net/gml""
   xmlns:ogc=""http://www.opengis.net/ogc""
   xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance""
   xsi:schemaLocation=""http://www.opengis.net/wfs http://schemas.opengis.net/wfs
/1.0.0/WFS-basic.xsd
                       http://www.ttt.org/myns http://barte/cgi-bin/mapserv.exe?
map=/ms4w/apps/general/map/basispakket.map&amp;SERVICE=WFS&amp;VERSION=1.0.0&amp
;REQUEST=DescribeFeatureType&amp;TYPENAME=bodemkaart250"">
   <gml:boundedBy>
      <gml:null>inapplicable</gml:null>
   </gml:boundedBy>
</wfs:FeatureCollection>

Maybe this behaviour chould be changed into the following to make it more
user-friendly, I propose 2 options:

1. do not add layers which don't have DUMP TRUE to the WFS capabilities at all
(maybe produce a warning in the capabilities). This also has implications for
DescribeLayer on the SLD WMS interface.
2. generate an exception instead of an empty null GML response stating that no
features are available because DUMP TRUE has not been set on the layer.

I would be in favour of option 1.
}}}"	defect	closed	high		WFS Server	4.3	normal	fixed