Let's say I am a maintainer of an EJB app. I deploy an EJB to JBoss EAP, and get hunderds of lines of stacktrace, from which I only need a single line:
No container configured with name 'Custom Message Driven Bean''
and the second most important information, WHERE that dependency comes from, is completely missing.
So i get 50 % of information I need packaged in useless repeatedly printed stacktraces (but that's other story).

Could the Ejb3AnnotationHandler put an information to the Exception's message about where did it dig the MDB reference from?

And, generally - could this be applied to all error messages?