I am trying get rid of web.xml and move to using WebApplicationInitializer.
Everything seems to be working fine except the startup time is now slow. Apparently the application server (tomcat 7 in my case) is searching all JARs in my WEB-INF/lib folder for the classes that implement WebApplicationInitializer. Since I have Spring/Hibernate setup that folder has lots of jars and it takes some time for the application server to find those JARs that have WebApplicationInitializer implementation. I am hoping there might be a way to explicitly point tomcat to the specific JARs and save time on JAR scanning.
Thoughts are greatly appreciated.
subject: Servlet 3.0, slow scan for WebApplicationInitializer