You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2013/07/18 08:48:50 UTC
[jira] [Resolved] (LOG4J2-299) Ability to retrieve original
Throwable from ThrowableProxy
[ https://issues.apache.org/jira/browse/LOG4J2-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-299.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0-beta9
getThrowable was added in revision 1504373. Please verify and close.
> Ability to retrieve original Throwable from ThrowableProxy
> ----------------------------------------------------------
>
> Key: LOG4J2-299
> URL: https://issues.apache.org/jira/browse/LOG4J2-299
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0-beta7
> Reporter: jeremy franklin-ross
> Fix For: 2.0-beta9
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> If ThrowableProxy is to exist without change, it would be polite to provide mechanism to retrieve the initial source Throwable in an unadulterated form.
> As already reported it's impossible to retrieve the original class name of the Throwable that was the source of a proxy instance, though the data exists as the private name attribute, which wouldn't be an issue at all if we could merely access the
> Say via something like:
> public Throwable proxiedThrown()
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org