WFS Metadata versus connection string (envdat WFS)

[Kralidis,Tom [Burlington]]

> 
> Tyler Mitchell wrote:
> > I'm working with this WFS data: 
> > 
> http://map.ns.ec.gc.ca/envdat/map.aspx?service=WFS&version=1.0.0&reque
> > st=GetCapabilities
> >
> > It works, but I'm a bit confused when using the data in my 
> map file.  
> > If I put the parameters manually into the connection string/URL, it 
> > works.  But if I put parameters like wfs_version, 
> wfs_request into the 
> > metadata section for the layer (and remove them from the URL) it 
> > doesn't seem to work anymore.
> >
> 
> Are you using 4.2 or 4.4?
> 
> If you are using 4.4, then wfs_* metadata should be supported 
> (and the old method of passing everything in the CONNECTION 
> string deprecated), but unfortunately the WFS Client HOWTO 
> still hasn't been updated to reflect that. You may find some 
> useful hints in bug 417: 
> http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=417

Actually, I just tested this again with 4.4.0-beta2, and get the same
issues Tyler has (parameters embedded in CONNECTION work, parameters as
METADATA/wfs_* with no parameters in CONNECTION does not).

When I try this, .gml files are written to my temp directory.  Upon
checking these w.r.t. this issue, they all come back as OGC service
exceptions, like:

"VERSION keyword missing"

..and so on.

..Tom