What (if any) have you done to provide the user with more specific information on what went wrong when running across exceptions (more detailed than splitting them by type at pages.xml)?

One theory I had was to have a @ExceptionHandled that would extract information about the method and rethrow a custom exception. Other annotated methods would then add to the exception message stack to provide an overview what the execution path had been

Another theory was just to run everyting through to a common exception handle that would extract the same information from the final stack trace

In both cases the method descrption would be a @Decscription annotation or a resource bundle with classname.methodname as key.

This would enabled error messages like "There was en error saving the user. This was due to an error in the database. The error was 'ORA-00000 horror and terror'" with annotations or resource bundle entries.

Should the user even be bothered with such information?