So my preference would be to leave it as a RuntimeException.
Another option would be to change the limit from 1000 to Integer.MAX_VALUE. This would be more compatible, although we'd start getting complaints again from folks who run out of memory, or that things are really slow...
Sigh. Maybe we should just go with an IOException. That won't break existing applications, which already have to catch this.
Doug
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
