Failed to parse mapping resource......
2017-12-12 16:20
323 查看
每次项目跑不起来,报错一大堆,就很烦躁,其实应该试着沉下心来好好看报错信息,结合项目经验和对报错信息的分析,才能更高效的解决问题!
今天在mapper.xml中写了一个相对复杂的SQL语句,本以为成功近在咫尺,然而报错了。。像是大冷天一身暖和突然被浇盆冷水,有点失落了,然后盯着报错看了很久,但是却没有仔细看就急着复制到浏览器查找错误解决方法,一次次试运行,报错依在。。
Cannot resolve reference to bean 'sqlSessionFactory' while setting bean property 'sqlSessionFactory';
nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sqlSessionFactory' defined in class path resource [spring-mybatis.xml]: Invocation of init method failed;
nested exception is org.springframework.core.NestedIOException: Failed to parse mapping resource: 'file [D:\Program Files\apache-tomcat-8.5.23\wtpwebapps\pisms\WEB-INF\classes\mapper\***.xml]';
nested exception is org.apache.ibatis.builder.BuilderException: Error creating document instance. Cause: org.xml.sax.SAXParseException; lineNumber: 31; columnNumber: 14; 元素内容必须由格式正确的字符数据或标记组成。
其实报错信息里提示的很清楚,在这个XML文件中31行,14列有错误,导致XML文件无法解析,从而spring容器初始化失败。。
如果数据库配置么有问题,而某个映射文件中有错误,那么项目部署运行过程中,控制台输出日志信息中,按顺序解析映射文件时会到错误的映射文件停止并报错。。。
解析映射文件失败的原因也许有:
1.数据库中数据表有变化,而映射文件未更新
2.映射文件中SQL语句出错,所以最好先跑一遍SQL,如果没问题那可能是格式有问题,比如运算符等
今天在mapper.xml中写了一个相对复杂的SQL语句,本以为成功近在咫尺,然而报错了。。像是大冷天一身暖和突然被浇盆冷水,有点失落了,然后盯着报错看了很久,但是却没有仔细看就急着复制到浏览器查找错误解决方法,一次次试运行,报错依在。。
Cannot resolve reference to bean 'sqlSessionFactory' while setting bean property 'sqlSessionFactory';
nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sqlSessionFactory' defined in class path resource [spring-mybatis.xml]: Invocation of init method failed;
nested exception is org.springframework.core.NestedIOException: Failed to parse mapping resource: 'file [D:\Program Files\apache-tomcat-8.5.23\wtpwebapps\pisms\WEB-INF\classes\mapper\***.xml]';
nested exception is org.apache.ibatis.builder.BuilderException: Error creating document instance. Cause: org.xml.sax.SAXParseException; lineNumber: 31; columnNumber: 14; 元素内容必须由格式正确的字符数据或标记组成。
其实报错信息里提示的很清楚,在这个XML文件中31行,14列有错误,导致XML文件无法解析,从而spring容器初始化失败。。
如果数据库配置么有问题,而某个映射文件中有错误,那么项目部署运行过程中,控制台输出日志信息中,按顺序解析映射文件时会到错误的映射文件停止并报错。。。
解析映射文件失败的原因也许有:
1.数据库中数据表有变化,而映射文件未更新
2.映射文件中SQL语句出错,所以最好先跑一遍SQL,如果没问题那可能是格式有问题,比如运算符等
相关文章推荐
- mybatis运行返回Failed to parse mapping resource
- 4000 org.springframework.core.NestedIOException: Failed to parse mapping resource: 'file [XXX.xml]';
- eclipse中用Hibernate进行一对多级联报错 Could not parse mapping document from resource oneToMore/Grade.hbm.xml
- ES错误Error:Failed to parse mapping [data]:[_ttl] is removed in 5.0
- Java解析DBF文件,错误Failed to parse Number: For input string: "-.---" 或读取不出数据或乱码问题都在这里解决
- jenkins 启动slave,出现com.sun.deploy.net.FailedDownloadException: Unable to load resource
- Failed to load resource: the server responded with a status of 400 (Bad Request)
- ASM ClassReader failed to parse class file - probably due to a new Java class file version that isn'
- 集成swagger时出现failed to parse JSON/YAML response的问题
- Nginx反向代理上传大文件报错(failed to load resource : net :: ERR_CONNECTION_RESET)
- 异常信息ASM ClassReader failed to parse class file的问题解决
- Hadoop: Connecting to ResourceManager failed
- Failed to load resource: the server responded with a status of 504 (Gateway Time-out)
- PRCR-1065 Failed to stop resource ora.asm 处理
- 好困出来的bugFailed to load resource: the server responded with a status of 404 (Not Found)
- FAILED: ParseException line 4:2 Failed to recognize predicate 'user'. Failed rule: 'identifier' in c
- Ignore gsd resource failed to start above 10g
- Could not parse mapping document from resource cn/spt/model/Student.hbm.xml
- JsonMappingException: failed to lazily initialize a collection of role
- WARNING rally.common.broker [-] Failed to consume a task from the queue: The resource could not be found. (HTTP 404)