Address error: At least one JAR is scanned for TLDs yet contained no TLDs.

Problem Description: Background error

Info: At least one JAR is scanned for TLDs yet contained no TLDs. Enable debug logging for the logger for a complete list of JARs that were scanned and no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.

The log indicates that the jar that this log refers to is scanned TLDs, and no TLDs is found in it, and it is recommended to open the debug level log, view the relevant jar file, and ignore the TLDs scan of such a jar in the Tomcat configuration file.

Page error:getElementById () was passed an empty string argument.

Object { name: "Administrator", password: "123456" }, but the output is parameter-aware.

Encountered this problem, check the majority of Baidu is said to modify the Tomcat file or <!----> and so on, but to try it, it is useless. It's just your situation, but I don't know if your situation is like this.

Fortunately now solved, also is to give oneself a recollection remember later not two.

But also good is a colleague's reminder to say whether you set up the interception, and then went to see the configuration information.

Because Shiro is used for login verification, the security framework for Web. XML configuration Shiro has been commented out:

Run the project then reported an additional error: Org.apache.shiro.UnavailableSecurityManagerException:No SecurityManager accessible to the calling  Code, either bound to the Org.apache.shiro.util.ThreadContext or as a VM static singleton. This was an invalid application configuration.

Org.apache.shiro.UnavailableSecurityManagerException:NoSecurityManager can be accessed by the calling code, or bound to Org.apache.shiro.util.ThreadContext, to Bind as a VM static singleton, which is an invalid application configuration.

This time to look at the Spring-shiro.xml configuration file, only to find:

The request path to the login page is not added, and the path on the red line is OK. Hope can also help you!

Address error: At least one JAR is scanned for TLDs yet contained no TLDs.