https://issues.apache.org/bugzilla/show_bug.cgi?id=54065
--- Comment #3 from Mark Thomas <ma...@apache.org> --- (In reply to comment #2) > Thanks for the tip with the ContextConfig.jarsToSkip. That worked out well! > Of course that also disables web-fragment parsing, right? Answered in comment #1. > We have not been able to remove META-INF/resources though as this location > is used by other EE specs (e.g. JSF) since years. So there is practically no > way around this without breaking almost all JSF projects. Yes there is, ContextConfig.jarsToSkip. > Thus I still think you should investigate the performance. It's sad that > servlet-3.0 requires to lookup resources in JNDI upfront. This is not a Servlet 3.0 requirement but a consequence of how Tomcat implements resources. The implementation isn't going to change as it is already very fragile. It has been re-written for Tomcat 8 and the caching in the new implementation should handle this. > This is utter > expensive and really costs up to 20% of our performance. It's sad to see > that some EGs try to add as much features as possible without thinking about > the possible consequences. The Servlet EG members have very little say in what is in or out of the spec. Once Oracle decide a major feature is in/out then it is very hard to change that decision. > Maybe this can be solved via a negative cache > (remembering JNDI misses)? Or probably via an own configuration to disable > this behaviour? Again, ContextConfig.jarsToSkip -- 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
