您的位置:首页 > 编程语言 > Java开发

The type java.util.Map$Entry cannot be resolved. 问题解决

2017-05-27 18:04 471 查看
今天使用Eclipse搭建SpringMVC环境的时候,遇到一个Error:

An error occurred at line: 1 in the generated java file
The type java.util.Map$Entry cannot be resolved. It is indirectly referenced from required .class files

Stacktrace:
at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:92)
at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330)
at org.apache.jasper.
4000
compiler.JDTCompiler.generateClass(JDTCompiler.java:439)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:356)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:334)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:321)


本地环境:

java version “1.8.0_45”

apache-tomcat-6.0.35

Eclipse Java EE IDE for Web Developers. Version: Luna Service Release 2 (4.4.2)

解决办法:

国内网站简单查了下,全说降低JDK版本。没明白根本原因,然后在StackOverFlow找到解答。下面是链接。

StackOverFlow

里面这么说:

When using JDK 8 and an IDE with its own compiler, like Eclipse, you have to update the IDE to a version with Java 8 support, even if you are not using the newer Java 8 features.

The reason is that the [应该是指Eclipse] compiler must be able to load the newer class files of the JRE(应该是指JRE8) in order to compile your software which references these classes.

Sometimes you can get away with an older compiler when it ignores the newer version number of the class files. But some types will confuse older class file parsers as they use new features, notably(尤其是) AnnotatedElement, which now has default methods, and Map.Entry, an interface which now has static methods.

It seems that Eclipse does not make a difference between references for which no class file could be found and class files it failed to read when saying “«classname» cannot be resolved”.

可以看出,出问题的不是JRE/JDK什么的,是IDE的问题。

本地解决办法:

降级到JDK7,加入rt.jar到/WebContent/WEB-INF/lib下。
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息
标签: 
相关文章推荐