I am using Spring 3.1.2 along with javax.inject.jar on the class-path and I get the following message printed to my log files. I get these six lines of output for every web request to the application.
00:53:11,291 INFO [ClassPathScanningCandidateComponentProvider] JSR-330 'javax.inject.Named' annotation found and supported for component scanning
00:53:11,301 INFO [ClassPathScanningCandidateComponentProvider] JSR-330 'javax.inject.Named' annotation found and supported for component scanning
00:53:11,309 INFO [ClassPathScanningCandidateComponentProvider] JSR-330 'javax.inject.Named' annotation found and supported for component scanning
00:53:11,417 INFO [ClassPathScanningCandidateComponentProvider] JSR-330 'javax.inject.Named' annotation found and supported for component scanning
00:53:11,431 INFO [ClassPathScanningCandidateComponentProvider] JSR-330 'javax.inject.Named' annotation found and supported for component scanning
00:53:11,455 INFO [ClassPathScanningCandidateComponentProvider] JSR-330 'javax.inject.Named' annotation found and supported for component scanning
Question:
- Why is the above message being printed on every request?
- How to stop it from being printed on every request?
UPDATE: Here is how spring boots up:
<!-- Listeners that startup spring -->
<listener>
<listener-class>org.springframework.web.util.Log4jConfigListener</listener-class>
</listener>
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>
<listener>
<listener-class>org.springframework.security.web.session.HttpSessionEventPublisher</listener-class>
</listener>
<!-- main dispatcher servlet -->
<servlet>
<servlet-name>main</servlet-name>
<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>main</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
I am using JRebel and I am not sure if that starts extra contexts as part of its hacking the JVM and libraries to support live reload.
Any debug flags or categories I can configure to figure out where the problem is occurring?