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: > 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 >>> parsing problem. Seems the same problem occurs when editing >>> shapefiles. >> Hi Jesse, >> thanks for reporting, seems like a legitimate bug in xml parsing. >> Can you create a jira issue attaching the request, the stack trace, >> and a sample shapefile to reproduce the issue? >> >> Cheers >> Andrea > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > > !DSPAM:4007,480461e2180932085621377! > -- Justin Deoliveira The Open Planning Project [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
