I would like to be able to assign error codes, localize messages, provide context parameters, etc. before logging and generating events when configuration problems occur due to unavailable or missing resources when Spring creates all the beans.
How do I get in the middle of the exception handling? Am I stuck doing it in Log4j?
Tony


Reply With Quote