Justin Deoliveira ha scritto:
> The wfs spec says that when an attribute is null it should be committed
> as a property, instead of included an empty. I am not sure the latter is
> valid.
Right right... yet, what if for any strange reason the user really
wanted to provide an empty string as the
The wfs spec says that when an attribute is null it should be committed
as a property, instead of included an empty. I am not sure the latter is
valid.
However, I would say we should be lax in this case, I have run into the
same issue with openlayers wfs client as well.
Jesse Eichar wrote:
> W
Will do.
On 15-Apr-08, at 9:49 AM, Andrea Aime wrote:
> Jesse Eichar ha scritto:
>> Hi,
>> I've done some research for a uDig user. For Geoserver 1.6.3 uDig
>> can't add new features to a postgis via the WFS-T protocol. I've
>> tested 1.5.4 and it work fine. The problem seems to be an xml
Jesse Eichar ha scritto:
> Hi,
>
> I've done some research for a uDig user. For Geoserver 1.6.3 uDig can't
> add new features to a postgis via the WFS-T protocol. I've tested 1.5.4
> and it work fine. The problem seems to be an xml parsing problem.
> Seems the same problem occurs when editin
