DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22381>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22381 When an exception occurs during parsing with SAX, the file reference is not released [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2003-12-03 01:22 ------- I tried to reproduce the problem but it works fine for me. As written here, http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=998248 there's a try/finally block that ensure all the resources are closed. Since other people also seemed to fail to reproduce the problem, I'm going to mark this bug as WORKSFORME. If the submitter still believes that the problem exists, could you run the attached test case and see if it works or fails? Also, it would be nice if you can step-execute through the code (after you throw the exception) and see if the ParserConfiguration.cleanup method is invoked or not. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
