Should not be printing to stderr/stdout on exception.

eclipse-ee4j / jaxb-fi

Apache License 2.0

8 stars 10 forks source link

Should not be printing to stderr/stdout on exception. #34

Closed Tomas-Kraus closed 14 years ago

Tomas-Kraus commented 14 years ago

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]

Tomas-Kraus commented 5 years ago

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

Tomas-Kraus commented 14 years ago

@glassfishrobot Commented Reported by cakoose

Tomas-Kraus commented 14 years ago

@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"

Tomas-Kraus commented 14 years ago

@glassfishrobot Commented Was assigned to fi-issues

Tomas-Kraus commented 7 years ago

@glassfishrobot Commented This issue was imported from java.net JIRA FI-34

Tomas-Kraus commented 14 years ago

@glassfishrobot Commented Marked as fixed on Sunday, July 11th 2010, 7:59:08 pm