Hey Andreas,
Thanks, it works again when adding a geometryName to the protocol.
2 things:
1) this does change behaviour, so it would be important to document it
clearly in the release notes for 2.11 (if this makes it in there)
2) in the comments in ticked #3368, bartvde says:
"Maybe there is a WFS out there that needs PropertyName, but ignores
its value for WFS 1.0. But I think we can safely ignore until
someone files a bug with a case that fails. "
This is exactly the case for me with MS 6.0.x and 5.6.x too. MS needs a
PropertyName (can be anything so it seems!) and gives an error if it is
missing.
It's a small change for me to add geometryName (or featureNS) to the
protocol options. I'm just slightly concerned that there are more people
out there currently only using featurePrefix and featureType that might
not understand why their requests suddenly fail when using the new WFS
protocol behaviour.
Cheers,
Roald
On 17/07/11 03:24, Andreas Hocevar wrote:
Hey Roald,
what you describe is exactly the new expected behavior. However, if
you add either a featureNS or a geometryName, things should be working
again.
Let me know if you still have concerns, or if and where you think this
should be better documented. If the former, do you have a suggestion
how we could better solve this? Because the intention of the change
you suffer from was to make dynamic WFS configuration simpler.
Andreas.
On Jul 16, 2011 2:38 PM, "Roald de Wit" <l...@rdewit.net
<mailto:l...@rdewit.net>> wrote:
Hey Andreas,
It's true that I don't set the FeatureNS. However, I *do* set the
featureType *and* the featurePrefix in my protocol options, which
used to be sufficient.
If you take the wfs-protocol.html example from trunk and replace
featureNS with: featurePrefix: 'topp', you'll see that the
PropertyName disappears from the WFS request (in the BBOX filter).
Is this expected behaviour, ie: can I not use featurePrefix anymore
or is it a bug?
Thanks, Roald
On 16/07/11 19:59, Andreas Hocevar wrote:
>
>
> Hey Roald,
>
> the PropertyName will still always be set, unless you have a
poorly configured ...
>> On Jul 16, 2011 8:25 AM, "Roald de Wit" <l...@rdewit.net
<mailto:l...@rdewit.net> <mailto:l...@rdewit.net
<mailto:l...@rdewit.net>>> wrote:
>>
>> H...
d...@lists.osgeo.org <mailto:d...@lists.osgeo.org>
<mailto:d...@lists.osgeo.org <mailto:d...@lists.osgeo.org>>
>> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
_______________________________________________
Dev mailing list
d...@lists.osgeo.org <mailto:d...@lists.osgeo.org>
http://lists.o...
_______________________________________________
Dev mailing list
d...@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/openlayers-dev
