Hi,
I want to use the ExceptionHandler class for handling exception occurring in my webapp. I need to store the exception caught into the database, only display few info to the user and a unique ID for her to contact support if required. I think it is considered as quite a good practice, but I can't actually implement it using the current ExceptionHandler class implementation. The problem is: I can't get access to the application context (or any other context), so I can't get access to the connection pool of the container, so I can't make a proper connection to the database. I could make a jdbc connection to the database, but that would be as good practice as doing business logic in an Action (or worse). My point: I think the ExceptionHandler class should be improved with some way to access the Application Context. It looks like it has been designed to work completely out of the webapp and independently. I don't think it is good. Ideas how to make this work properly and comments are welcome (maybe I just missed the way to access the application context after all...). Regards, Seb'
