I’m trying to debug why certain handlers in one of my controllers is not invoked by Spring’s AnnotationMethodHandlerAdapter. I don’t get any errors in Netbeans, just a 404 in the browser. I tried placing a breakpoint in one of my working controllers/handlers then walking up the chain to place a breakpoint in the dispatcher.
Netbeans shows me some funny method bodies:
protected ModelAndView invokeHandlerMethod(HttpServletRequest request, HttpServletResponse response, Object handler) throws Exception
{
//compiled code
throw new RuntimeException("Compiled Code");
}
which I suspect is caused by the AOP magiq. Undeterred, I tried to configure log4j to trace the calls and display any messages logged at debug level from the org.springframework.web.servlet.mvc.annotation package, but just by creating a log4j.properties file and putting in the classpath I get nothing more than the default “INFO:” level messages. Adding the context-param and listener in web.xml fails because the container can’t find the log4j classes, even though they are there and even though I can add them again to the project.
So, the question is — what do I need to do to get method traces (this could be done through AOP) and enhanced debugging (this definitely needs log4j) under Spring 3.0?
If I’m not mistaken Spring 3.X uses SLF4J for logging. Usually you would need to add SLF4J binding for your logging framework of choice – for example, for log4, slf4j-log4j12 jar should be present in classpath as well as log4j.jar and they better be proper versions – I found SLF4J to be picky about that. See more details here. Also don’t forget log4j.xml config.