Java applications typically log execution steps in a log file. This includes exceptions as well (
a sample). The log files are usually collected after reproducing the error scenario and analyzed. So these can be large. next-error command can take one straight to the stacktrace location. Using the file and line number, one can figure out possible causes of errors. If one could click on it and reach the destination, it's even better.
I'm using this for jumping into code while running debug sessions with GUD. EDE just has a handy API for finding file by name. That's why I used that as an example.