News for hackers. Stuff that matters.
Re:Java call stack – from HTTP upto JDBC as a picture (2006) by marktangotango on Wednesday March 07, 2018 @07:55PM (#16541371)
Debugging these stack traces is easy, just look for your packages and classes, and “caused by”. You should never be debugging framework code. Well almost never.
Re:Java call stack – from HTTP upto JDBC as a picture (2006) by peterevans on Wednesday March 07, 2018 @08:56PM (#16541655)
"Almost never."

In my experience, the code you write within a third-party framework rarely works the way you expect it to the first time. So you often do "debug" the framework, just to see where your code goes while in the framework to see what you missed.

That's not a bad thing, though--it's a great way to learn any new framework!

Re:Java call stack – from HTTP upto JDBC as a picture (2006) by givehimagun on Wednesday March 07, 2018 @09:48PM (#16541882)
Agreed and I will piggyback on top of it. I think we forget how reliable some of the code in this stack is. It's battle-hardened and works extremely well with lots of documentation/help.

There is no sane alternative to this...that is the power of open source where we collectively pool our capacity into something worthwhile to everyone. I want more of it.

Re:Java call stack – from HTTP upto JDBC as a picture (2006) by jdmichal on Wednesday March 07, 2018 @09:54PM (#16541906)
Using jBPM, you get a NullPointerException when you use a WorkItemHandler with a BPMN <serviceTask>. Not a nice one with a message, either. Had to debug into jBPM to figure out that one.