[
http://jira.qos.ch/browse/LBCLASSIC-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10836#action_10836
]
Joern Huxhorn commented on LBCLASSIC-72:
----------------------------------------
Ok, my comments are a bit mixed right now.
The comments above about Throwable should be in LBCLASSIC-46 while my
explanation why I need access to the unformatted, raw StackTraceElement data is
at the right place right here.
Should I copy my above comment over?
Sorry but I somehow expected that StackTraceElementProxy would be used in
ThrowableProxy as a Throwable does contain StackTraceElements. That caused the
mix-up.
> Please implement a getter for StackTraceElementProxy.ste
> --------------------------------------------------------
>
> Key: LBCLASSIC-72
> URL: http://jira.qos.ch/browse/LBCLASSIC-72
> Project: logback-classic
> Issue Type: Improvement
> Reporter: Joern Huxhorn
> Assignee: Logback dev list
>
> I just checked out your latest changes concerning package version information
> because I have to implement it for Lilith when the next version of Logback is
> released.
> At the moment StackTraceElementProxy does not have a getter for the contained
> StackTraceElement. It would be really helpful for me if I could access it.
> Otherwise I'd have to parse it from steAsString which I'd really like to
> prevent.
> I'd suggest to implement both a getter and a setter for the StackTraceElement.
> steAsString would need to be set to null if the STE is changed.
> Additionally, I'd suggest to make steAsString transient since it can be
> restored after deserialization.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-dev
