如何修复JSP编译器警告:一个JAR已扫描TLD,但不包含TLD? [英] How to fix JSP compiler warning: one JAR was scanned for TLDs yet contained no TLDs?

查看:1181
本文介绍了如何修复JSP编译器警告:一个JAR已扫描TLD,但不包含TLD?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

当启动应用程序或通过ant编译JSP时,Tomcat 7 Jasper抱怨过多的或放错的JAR文件。我收到了以下消息

  ** compile-jsp:** 
[jasper] 2012年7月31日7:15 :15 PM org.apache.jasper.compiler.TldLocationsCache tldScanJar
[jasper] INFO:至少扫描了一个JAR,但没有包含TLD。为此记录器启用调试日志记录以查找已扫描但未在其中找到TLD的完整JAR列表。在扫描期间跳过不需要的JAR可以提高启动时间和JSP编译时间。

如何在扫描期间跳过不需要的JAR可以提高tomcat中的启动时间和JSP编译时间?

/ strong>,我不得不添加以下行到tomcat / conf / logging.properties为Tomcat扫描的jar显示在日志中:

  org.apache.jasper.servlet.TldScanner.level = FINE 


When starting the application or compiling JSP via ant, Tomcat 7 Jasper complains about superfluous or misplaced JAR file. I got below message

**compile-jsp:**
   [jasper] Jul 31, 2012 7:15:15 PM org.apache.jasper.compiler.TldLocationsCache tldScanJar
   [jasper] INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. 

how to Skipping unneeded JARs during scanning can improve startup time and JSP compilation time in tomcat?

how to enable better output?

解决方案

For Tomcat 8, I had to add the following line to tomcat/conf/logging.properties for the jars scanned by Tomcat to show up in the logs:

org.apache.jasper.servlet.TldScanner.level = FINE

这篇关于如何修复JSP编译器警告:一个JAR已扫描TLD,但不包含TLD?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆