Daniel,<div><br></div><div>You're right, the template is acting as the controller for the html format so there's no need to put the include/exclude items on top of it. I was just trying to found out the safest (and the easiest) way to control my data before exposing it.</div>
<div><br></div><div><div>In a real case scenario, if a table structure beyond a layer change, I will have to modify the html template but also all the wms|ows|gml include items. It's not such a big deal but since we have around 300 layer to maintain, It would been convenient to have a unique list of field to updated. It would also reduce the risk of error (ex: allowing one field in the gml mode but not in the html mode)</div>
<div><br></div><div>thanks again Daniel for your comments.</div><div><br></div><div>MartinO</div><div><br></div><div>2009/11/19 Daniel Morissette <span dir="ltr"><<a href="mailto:dmorissette@mapgears.com">dmorissette@mapgears.com</a>></span></div>
</div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">Martin Ouellet wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
3) GetFeatureInfo with INFO_FORMAT=text/html<br>
Result: the only required tag is TEMPLATE (a dummy file will return no data). But if you supply a valid html template, ALL the field will be returned because the METADATA tag ows_<include|exclude>_items or wms_<include|exclude>_items are ignored. So if my layer is a Oracle spatial table, I must then create a view to expose only the field I want. Would it be relevant to control the field with the "wms_include_items" tag ? Is there a reason why is not working that way?<br>
<br>
</blockquote>
<br></div>
When you use a HTML template, it is the template itself that controls which fields are returned, so I am not sure to understand the benefit of supporting the include/exclulde items on top of that.<br>
<br>
Are you saying that there is a situation where all the fields end up being unexpectedly dumped into the template out of your control? Maybe there is a hidden feature I am not aware of in the template processor, if that's the case then could you please elaborate?<br>
<br>
Daniel<br><font color="#888888">
-- <br>
Daniel Morissette<br>
<a href="http://www.mapgears.com/" target="_blank">http://www.mapgears.com/</a><br>
_______________________________________________<br>
mapserver-users mailing list<br>
<a href="mailto:mapserver-users@lists.osgeo.org" target="_blank">mapserver-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>
</font></blockquote></div><br></div>