This week's book giveaway is in the OCMJEA forum.
We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line!
See this thread for details.
The moose likes Servlets and the fly likes Servlet 3.0, slow scan for WebApplicationInitializer Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Java » Servlets
Bookmark "Servlet 3.0, slow scan for WebApplicationInitializer" Watch "Servlet 3.0, slow scan for WebApplicationInitializer" New topic
Author

Servlet 3.0, slow scan for WebApplicationInitializer

yuri cherio
Greenhorn

Joined: Sep 01, 2011
Posts: 1
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.
 
Consider Paul's rocket mass heater.
 
subject: Servlet 3.0, slow scan for WebApplicationInitializer