DeadockDetection: print stack trace of waitingResource?

SourceForge Submitter: sflexus .
It is very good that ApplicationDeadlockException is now
very verbose. However, it would make finding the
deadlock cause a piece of cake if it also would include
stack trace of the other (waiting) thread. If the
application is complex, only knowing two bean names is
not enough for me to guess where was the other place
that current transaction deadlocked with.