https://issues.apache.org/bugzilla/show_bug.cgi?id=52326
--- Comment #6 from Chris Beams <cbe...@gmail.com> 2012-01-02 07:24:44 UTC --- Hi Konstantin, Right, the 'metadata-complete' attribute has been around for a while, but when used against Servlet 3.0+, its semantics expand to mean that ServletContainerInitializer processing is skipped altogether. For users experiencing long startup times due to ServletContainerInitializer classloading overhead, metadata-complete="true" provides a simple way of avoiding the problem. Of course, the trouble is that these users may actually want or need to use ServletContainerInitializer functionality, for example taking advantage of Spring 3.1's WebApplicationInitializer support[1]. As long as SCI processing involves expensive classloading, larger applications will suffer from long startup times and thus be encouraged to "shut off" this functionality via metadata-complete="true". Thanks, Chris [1] http://static.springsource.org/spring/docs/3.1.x/javadoc-api/org/springframework/web/WebApplicationInitializer.html -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
