[
https://issues.apache.org/jira/browse/THRIFT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694769#action_12694769
]
David Reiss commented on THRIFT-416:
------------------------------------
001 has some odd changes to whitespace. Please revert them.
I'm hesitant to add a mandatory dependency to Thrift without significant
improvements in functionality. Is it possible to configure JUL at runtime to
use log4j as a backend or something like that? Are there JUL adapters for
log4j classes so we can just allow the servers to receive their logger as an
argument rather than instantiate a JUL logger?
> java.util.logging eats exceptions without warning
> -------------------------------------------------
>
> Key: THRIFT-416
> URL: https://issues.apache.org/jira/browse/THRIFT-416
> Project: Thrift
> Issue Type: Bug
> Components: Library (Java)
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Attachments:
> 0001-allow-exceptions-to-propagate-up-where-feasible.-on.patch,
> 0002-switch-to-log4j.patch
>
>
> Using java.util.logging has two related problems.
> One is that virtually no java project in the wild uses it. Everyone uses the
> more advanced log4j.
> Two is that unlike log4j, java.util.logging does not warn you when it is
> swallowing errors because it has not been configured.
> So thrift exceptions vanish without a trace which is bad.
> Here is a patch to switch to log4j.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
