Should not be printing to stderr/stdout on exception.
Tomas-Kraus opened this issue · comments
src/com/sun/xml/fastinfoset/stax/StAXDocumentParser.java, method next()
Near the bottom of the method, the code catches exceptions, prints out a stack
trace, then rethrows. Why is the stack trace being printed? It seems like a
bad idea for a library to dump stack traces to stdout/stderr.
My situation: I'm calling code that uses FI. If that code crashes with an
exception, I log it to a file and continue. It would be nice if FI didn't
pollute stdout/stderr.
Environment
Operating System: All
Platform: All
Affected Versions
[current]
- Issue Imported From: https://github.com/javaee/metro-fi/issues/34
- Original Issue Raised By:@glassfishrobot
- Original Issue Assigned To: @glassfishrobot
- Original Issue Closed By:@glassfishrobot
@glassfishrobot Commented
Reported by cakoose
@glassfishrobot Commented
oleksiys said:
fixed on 1.2.x trunk.
Tag: FastInfoset-1_2-branch
User: oleksiys
Date: 2010-07-12 09:55:22+0000
Modified:
fi/FastInfoset/src/com/sun/xml/fastinfoset/sax/SAXDocumentParser.java
fi/FastInfoset/src/com/sun/xml/fastinfoset/tools/SAX2StAXWriter.java
fi/FastInfoset/src/com/sun/xml/fastinfoset/stax/StAXDocumentParser.java
Log:
fix issue #34
https://fi.dev.java.net/issues/show_bug.cgi?id=34
"Should not be printing to stderr/stdout on exception"
@glassfishrobot Commented
Was assigned to fi-issues
@glassfishrobot Commented
This issue was imported from java.net JIRA FI-34
@glassfishrobot Commented
Marked as fixed on Sunday, July 11th 2010, 7:59:08 pm