You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed the same issue as described in #224. The PDF I'm generating works, but there's a fairly long stack trace that is visible on the standard error every time I generate this PDF.
The exception that causes this stack trace is effectively invisible and ignored by the calling application, while the printStackTrace() statement just displays it on the standard error. It makes perfect sense to have these statements for quick development, but once this library is used in an application, they just put more noise in the standard error logs (if captured), and are completely separate from that application's logging system.
Perhaps they should either be removed altogether (to make those exceptions fail silently) or, better, use a logging framework (e.g. com.openhtmltopdf.util.XRLog) to log them with debug or warning levels.
There seems to be about 20 or so occurrences like these:
I've noticed the same issue as described in #224. The PDF I'm generating works, but there's a fairly long stack trace that is visible on the standard error every time I generate this PDF.
The exception that causes this stack trace is effectively invisible and ignored by the calling application, while the
printStackTrace()
statement just displays it on the standard error. It makes perfect sense to have these statements for quick development, but once this library is used in an application, they just put more noise in the standard error logs (if captured), and are completely separate from that application's logging system.Perhaps they should either be removed altogether (to make those exceptions fail silently) or, better, use a logging framework (e.g.
com.openhtmltopdf.util.XRLog
) to log them with debug or warning levels.There seems to be about 20 or so occurrences like these:
The text was updated successfully, but these errors were encountered: