• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Servlet 3.0, slow scan for WebApplicationInitializer

 
Greenhorn
Posts: 1
Eclipse IDE Postgres Database Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
A sonic boom would certainly ruin a giant souffle. But this tiny ad would protect it:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic