Download [#FI-34] Should not be printing to stderr/stdout on exception.

[FI-34] Should not be printing to stderr/stdout on exception. Created: 11/Jul/10
12/Jul/10 Resolved: 12/Jul/10
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Resolved
fi
core
current
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Environment:
Bug
cakoose
Fixed
None
Not Specified
Issuezilla Id:
34
1.2.9
Priority:
Assignee:
Votes:
Major
fi-issues
0
Not Specified
Not Specified
Operating System: All
Platform: All
Description
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.
Comments
Comment by oleksiys [ 12/Jul/10 ]
fixed on 1.2.x trunk.
Updated:
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"
Generated at Fri May 12 01:08:48 UTC 2017 using JIRA 6.2.3#6260sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.