[logback-dev] [JIRA] Commented: (LBCLASSIC-72) Please implement a getter for StackTraceElementProxy.ste

Joern Huxhorn (JIRA) noreply-jira at qos.ch
Tue Oct 28 19:39:21 CET 2008

    [ http://jira.qos.ch/browse/LBCLASSIC-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10834#action_10834 ] 

Joern Huxhorn commented on LBCLASSIC-72:

I need the Throwable structure intact because I'd like to be able to decide - on the fly - how they are displayed.

I need several different representations for different cases, e.g. the Throwable column in the table view of Lilith, the detailsView of the message (which is fully customizable by the user himself if he wants to do the work and knows some Groovy) or the IDEA (or, more generally, IDE) integration feature that jumps to the line of code if the link is clicked in the detailsView.

All those expect an ordinary StackTraceElement. My latest version uses an ExtendedStackTraceElement that contains your additional location infos but is also easily tranformed back into a simple StackTraceElement again for transmission to the IDE of choice.

Well, that's the reason why I'd really appreciate to be able to access the unformatted raw information. Otherwise I'm forced to parse the created String. I also desperately need the infos because of the XML structure used to transfer the events in a java-independent manner. I plan to also be able to receive LoggingEvents from Flash and C# using just that XML structure.

Regards, Joern.

> 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


More information about the logback-dev mailing list