Comments on: Have you hugged your StackTraceElement today? http://blog.kischuk.com/2005/01/07/have-you-hugged-your-stacktraceelement-today/ Just another WordPress.com weblog Wed, 03 Mar 2010 19:20:46 +0000 http://wordpress.com/ hourly 1 By: Daniel Marchant http://blog.kischuk.com/2005/01/07/have-you-hugged-your-stacktraceelement-today/#comment-61 Daniel Marchant Mon, 10 Jan 2005 10:38:33 +0000 http://rkischuk.wordpress.com/2005/01/07/have-you-hugged-your-stacktraceelement-today/#comment-61 I have used it in the past for debugging purposes while trying to solve some pretty bad bugs. Other then that it is convenient for filtering of what parts of the stack trace you want to see. Log space is cheap but sometimes if you can filter on the output it helps in weeding through the logs during production issues. Not sure I would tell a lot of people about it though. It seems it could be pretty dangerous in the wrong hands. Some people might use it for a java GOTO style programming for the business logic. If the stack trace contains "com.blah.logic" go to another object and call a method. The aspect technique might be an idea as well. Just aspect a filter if you needed it. I have used it in the past for debugging purposes while trying to solve some pretty bad bugs. Other then that it is convenient for filtering of what parts of the stack trace you want to see. Log space is cheap but sometimes if you can filter on the output it helps in weeding through the logs during production issues.

Not sure I would tell a lot of people about it though. It seems it could be pretty dangerous in the wrong hands. Some people might use it for a java GOTO style programming for the business logic. If the stack trace contains “com.blah.logic” go to another object and call a method.

The aspect technique might be an idea as well. Just aspect a filter if you needed it.

]]>