Opps I am pretty sure you intended this to go to the list; you are mostly going to be interacting with others the community on this one - at the very least because I cannot think where to start ;-)
Jody > Hello Jody, > > I think there ist another problem. > The issue ocuurs at the first feature which will be read by the > getFeatureReader(..) method. > This will stop the complete operation. > > I think your solution with the null value sounds good. > Another way would be to check the nil-Attribute at the Elements an only set > the value to null if bil = true. > Do you have got an place where can I can insert it into the Code? > I will try to create a patch an when everything works fine I will send it to > you. > > Tim > > > > -----Ursprüngliche Nachricht----- > Von: Jody Garnett [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 15. November 2007 21:39 > An: Tim Englich > Betreff: Re: [Geotools-devel] WFS-Plugin: Features with Numeric > Attribute which value is nil fail to read in GetFeature-Request > > > I think we should should use null for the value if an empty string was > provided. But I am fond of logging a warning > and moving on; even in the case where data is invalid. The current > solution of throwing an exception is okay > as long as the client code us using a try/catch around their feature > read - they can log the fact that on of their > features was invalid and could not be used; and move onto the next ... > > Jody > > Tim Englich wrote: > >> Hello, >> >> I have got a problem using the WFS-Plugin. >> When I try to fetch Features from a WFS which has got a numeric Element >> > which > >> is nil I get the following Exception: >> >> WARNUNG: java.io.IOException: org.xml.sax.SAXException: For input string: >> > "" > >> [Fatal Error] :-1:-1: Premature end of file. >> >> I have take a look into GeoTools-Sourcecode of the trunk and saw that a >> NumberFormatException will be thrown in >> org.geotools.xml.xsi.XSISimpleTypes.Integer.getValue(...) if there is no >> valid Value. >> I take also a look at the other numeric value parsers. No Implementation >> handle the NumberFormatException correctly. >> >> How can we generally solve this Problem? >> >> Thanks a lot >> Tim >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Geotools-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/geotools-devel >> >> > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
