Hi, I had a strange issue today with GeoServer. Trying out a request that would end up making a feature collection, and passing it to FreeMarker I got a long stack trace that basically just complained that an iterator said there were features, just to throw an exception when calling next()...
At first I was quite baffled because the above exception was not really returning me any info. Debugging the code I noticed that if an exception occurred trying to create the iterator in DataFeatureCollection a new NoContentIterator holding the exception was created. That iterator returned true to hasNext(), and then threw the exception it was holing on next(). This look very odd to me, why not throw the exception directly when creating the iterator? Freemarker has certainly a share of blame, but if that would have happened on a user site I the log would have been totally uninformative to me. Can't we just kill NoContentIterator and throw the exception in the very place where it did originate? Cheers Andrea ------------------------------------------------------------------------- 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
