org.xml.sax.SAXParseException:src-import.0:阅读导入模式文档"null"失败 解决方案

最新推荐文章于 2024-08-12 22:17:50 发布
原创 最新推荐文章于 2024-08-12 22:17:50 发布 · 362 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#xercesimpl #spring3 #sax #saxparseexception

本文提供了解决Spring加载时抛出的SAX解析异常的方法，通过更新xercesImpl.jar文件来解决导入模式文档读取失败的问题。
Spring加载时抛了这样一个错：
org.xml.sax.SAXParseException:src-import.0:阅读导入模式文档"null"失败 解决方案

解决方案也不难，更新xercesImpl.jar，貌似在Spring官方下载的那个xercesImpl.jar有点老了。

这里提供一个新点的xercesImpl.jar， 只针对Spring3。
IntelliJ IDEA调用webservice出现异常org.xml.sax.SAXException
weixin_40857929的博客
11-29 2546
org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize. 客户端代码： package test; import example.HelloWorld; import org...
org.xml.sax.SAXParseException: src-import.0: Failed to read imported schema document 'null'
风雨同舟
04-11 1588
公司项目用的是ssh，最近发现每次tomcat启动的时候，控制台总是出现下面的这个异常2015-04-10 09:13:50 [org.springframework.web.context.ContextLoader]-[INFO] - Root WebApplicationContext: initialization started 2015-04-10 09:13:50 [org.sprin
org.xml.sax.SAXParseException: Failed to read schema document 的原因分析与解决方法
weixin_33922670的博客
08-14 315
现象: org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema documen t 'http://www.springframework.org/schema/beans/spring-beans-3.1.xsd', because 1) could not find the document...
解决resin的org.xml.sax.SAXParseException问题
weixin_34090643的博客
08-06 178
公司OA系统使用resin服务，更新性能补丁包以后，出现org.xml.sax.SAXParseException:Invalidencodingname"GBK"的问题，导致外部数据源不可用。 2012-08-03 13:09:42,576 ERROR org.apache.hivemind.impl.XmlModuleDescriptorProvider - ...
android下载xml解析 文件尾出现NUL 导致解析异常的解决方法
weixin_34087503的博客
11-16 557
我在做一个项目时发现：当我用常用的下载方法 下载xml到sd卡中 然后读取xml解析时 总是有如下异常： 但程序仍能运行 只是xml解析后的条数变少了 我觉得应该是解析过程中遇到了不能解析的字符 但检查服务器端的xml并未发现错误 （我还曾一度认为是网络不佳导致的，现在想象真是可笑的误区） 之后我检查了下载到本地sd卡的xml文件，用notepad打开后 错误发现了...
08-22 16:18:28.088 ERROR [ContextLoader.java:172] Context initialization failed org.springframework.beans.factory.BeanDefinitionStoreException: Line 5 in XML document from class path resource [com/sap/apps/sapInterface/test_context_sap.xml] is invalid; nested exception is org.xml.sax.SAXParseException: Document root element "beans", must match DOCTYPE root "null".
08-23
首先，用户的问题是关于解决Spring上下文初始化失败的错误，具体是："XML root element beans mismatch DOCTYPE null error"。从系统指令中，我有几个引用可以参考。 回顾引用： - 引用[1]：提到一个XML解析错误，...
org.xml.sax.SAXParseException; systemId
06-12
我们遇到了一个与XML解析相关的异常：org.xml.sax.SAXParseException，并且提到了systemId。这个异常通常在使用SAX解析器解析XML文档时发生，表示在解析过程中遇到了问题。异常信息中提到的systemId通常是XML文档的...
fr.opensagres.poi.xwpf.converter.core.XWPFConverterException: org.apache.xmlbeans.XmlException: error: Unexpected end of file after null at fr.opensagres.poi.xwpf.converter.pdf.PdfConverter.doConvert(PdfConverter.java:71) at fr.opensagres.poi.xwpf.converter.pdf.PdfConverter.doConvert(PdfConverter.java:39) at fr.opensagres.poi.xwpf.converter.core.AbstractXWPFConverter.convert(AbstractXWPFConverter.java:46) at com.qdwk.DocxToPdfConverter.convertWordToPdfInChunks(DocxToPdfConverter.java:160) at com.qdwk.DocxToPdfConverter.main(DocxToPdfConverter.java:129) Caused by: org.apache.xmlbeans.XmlException: error: Unexpected end of file after null at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3511) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1277) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1264) at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345) at org.openxmlformats.schemas.wordprocessingml.x2006.main.StylesDocument$Factory.parse(Unknown Source) at org.apache.poi.xwpf.usermodel.XWPFDocument.getStyle(XWPFDocument.java:464) at fr.opensagres.poi.xwpf.converter.core.styles.XWPFStylesDocument.<init>(XWPFStylesDocument.java:194) at fr.opensagres.poi.xwpf.converter.core.styles.XWPFStylesDocument.<init>(XWPFStylesDocument.java:188) at fr.opensagres.poi.xwpf.converter.core.XWPFDocumentVisitor.createStylesDocument(XWPFDocumentVisitor.java:151) at fr.opensagres.poi.xwpf.converter.core.XWPFDocumentVisitor.<init>(XWPFDocumentVisitor.java:144) at fr.opensagres.poi.xwpf.converter.pdf.internal.PdfMapper.<init>(PdfMapper.java:138) at fr.opensagres.poi.xwpf.converter.pdf.PdfConverter.doConvert(PdfConverter.java:56) ... 4 more Caused by: org.xml.sax.SAXParseException; systemId: file:; lineNumber: 1; columnNumber: 1; Unexpected end of file after null at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportFatalError(Piccolo.java:1038) at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:723) at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3479) ... 15 more 现在出现这样的问题
最新发布
10-10
`fr.opensagres.poi.xwpf.converter.core.XWPFConverterException: org.apache.xmlbeans.XmlException: error: Unexpected end of file after null` 错误通常表示在解析 DOCX 文件的 XML 内容时，文件提前结束，可能...
异常分析：11:07:40.137 [main] DEBUG org.apache.cxf.common.logging.LogUtils - Using org.apache.cxf.common.logging.Slf4jLogger for logging. 11:07:40.294 [main] DEBUG org.apache.cxf.endpoint.dynamic.DynamicClientFactory - Creating client from WSDL https://znwc.cnooc/xcoa/services/WsOaSystemService?wsdl 11:07:40.368 [main] DEBUG org.apache.cxf.resource.DefaultResourceManager - resolving resource <org.apache.cxf.wsdl11.WSDLManagerImpl/bus> type <interface org.apache.cxf.Bus> 11:07:40.369 [main] DEBUG org.apache.cxf.resource.DefaultResourceManager - resolving resource <null> type <interface org.apache.cxf.Bus> 11:08:30.898 [main] DEBUG org.apache.cxf.transport.http.HTTPConduit - Conduit &#39;{http://cxf.apache.org}TransportURIResolver.http-conduit&#39; has been (re)configured for plain http. 11:08:30.908 [main] DEBUG org.apache.cxf.transport.http.HTTPConduit - No Trust Decider configured for Conduit &#39;{http://cxf.apache.org}TransportURIResolver.http-conduit&#39; 11:08:30.910 [main] DEBUG org.apache.cxf.transport.http.HTTPConduit - No Auth Supplier configured for Conduit &#39;{http://cxf.apache.org}TransportURIResolver.http-conduit&#39; 11:08:30.911 [main] DEBUG org.apache.cxf.transport.http.HTTPConduit - Conduit &#39;{http://cxf.apache.org}TransportURIResolver.http-conduit&#39; has been configured for plain http. 11:08:30.921 [main] DEBUG org.apache.cxf.transport.http.HTTPConduit - registering incoming observer: org.apache.cxf.transport.TransportURIResolver$1@34a97744 11:08:31.184 [main] DEBUG org.apache.cxf.transport.https.SSLUtils - The location of the key store has not been set via a system parameter or through configuration so the default value of C:\Users\smartdot/.keystore will be used. 11:08:31.188 [main] DEBUG org.apache.cxf.transport.https.SSLUtils - The key store password has not been set via a system property or through configuration, reading data from the keystore will fail. 11:08:31.191 [main] DEBUG org.apache.cxf.transport.https.SSLUtils - The key password has not been set via a system property or through configuration, reading data from the keystore will fail. 11:08:31.193 [main] DEBUG org.apache.cxf.transport.https.SSLUtils - The keystore type has not been set in configuration so the default value of JKS will be used. 11:08:31.598 [main] DEBUG org.apache.cxf.resource.DefaultResourceManager - resolving resource <C:\Users\smartdot/.keystore> as stream 11:08:31.693 [main] DEBUG org.apache.cxf.transport.https.SSLUtils - No default keystore C:\Users\smartdot/.keystore 11:08:31.696 [main] DEBUG org.apache.cxf.transport.https.SSLUtils - The location of the trust store has not been set via a system parameter or through configuration so the default value of null will be used. 11:08:31.698 [main] DEBUG org.apache.cxf.transport.https.SSLUtils - TRUST_STORE_PASSWORD_NOT_SET 11:08:31.700 [main] DEBUG org.apache.cxf.transport.https.SSLUtils - The trust store type has not been set in configuration so the default value of JKS will be used. 11:08:31.767 [main] DEBUG org.apache.cxf.transport.https.HttpsURLConnectionFactory - The cipher suites have been set to [TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384, TLS_DHE_RSA_WITH_AES_256_CBC_SHA256, TLS_DHE_DSS_WITH_AES_256_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_DSS_WITH_AES_128_GCM_SHA256, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]. 11:08:33.321 [main] DEBUG org.apache.cxf.transport.http.Headers - Accept: */* 11:08:33.322 [main] DEBUG org.apache.cxf.transport.http.HTTPConduit - No Trust Decider for Conduit &#39;{http://cxf.apache.org}TransportURIResolver.http-conduit&#39;. An affirmative Trust Decision is assumed. 11:10:47.826 [main] DEBUG org.apache.cxf.transport.http.HTTPConduit - Conduit &#39;{http://cxf.apache.org}TransportURIResolver.http-conduit&#39; has been (re)configured for plain http. 11:10:47.830 [main] DEBUG org.apache.cxf.transport.http.HTTPConduit - No Trust Decider configured for Conduit &#39;{http://cxf.apache.org}TransportURIResolver.http-conduit&#39; 11:10:47.832 [main] DEBUG org.apache.cxf.transport.http.HTTPConduit - No Auth Supplier configured for Conduit &#39;{http://cxf.apache.org}TransportURIResolver.http-conduit&#39; 11:10:47.834 [main] DEBUG org.apache.cxf.transport.http.HTTPConduit - Conduit &#39;{http://cxf.apache.org}TransportURIResolver.http-conduit&#39; has been configured for plain http. 11:10:47.836 [main] DEBUG org.apache.cxf.transport.http.HTTPConduit - registering incoming observer: org.apache.cxf.transport.TransportURIResolver$1@62d0ac62 11:10:47.841 [main] DEBUG org.apache.cxf.transport.http.Headers - Accept: */* 11:10:47.842 [main] DEBUG org.apache.cxf.transport.http.HTTPConduit - No Trust Decider for Conduit &#39;{http://cxf.apache.org}TransportURIResolver.http-conduit&#39;. An affirmative Trust Decision is assumed. [Fatal Error] WsOaSystemService?wsdl=WsOaSystemService.wsdl:6:3: The element type "hr" must be terminated by the matching end-tag "</hr>". [2025-07-16 11:12:00] 错误: 服务调用失败 异常类型: ServiceConstructionException 错误详情: [Ljava.lang.String;@55caeb35 完整堆栈追踪: org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service. at org.apache.cxf.wsdl11.WSDLServiceFactory.<init>(WSDLServiceFactory.java:76) at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicClientFactory.java:319) at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicClientFactory.java:245) at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicClientFactory.java:238) at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicClientFactory.java:192) at com.hd.xcoa.project.BasicAuthWebServiceClient.createSecureClient(BasicAuthWebServiceClient.java:94) at com.hd.xcoa.project.BasicAuthWebServiceClient.main(BasicAuthWebServiceClient.java:33) Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:import): faultCode=PARSER_ERROR: Problem parsing &#39;http://znwc.cnooc/xcoa/services/WsOaSystemService?wsdl=WsOaSystemService.wsdl&#39;.: org.xml.sax.SAXParseException: The element type "hr" must be terminated by the matching end-tag "</hr>". at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2198) at com.ibm.wsdl.xml.WSDLReaderImpl.parseImport(WSDLReaderImpl.java:435) at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(WSDLReaderImpl.java:312) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2352) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2338) at org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:255) at org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:165) at org.apache.cxf.wsdl11.WSDLServiceFactory.<init>(WSDLServiceFactory.java:74) ... 6 more Caused by: org.xml.sax.SAXParseExceptionpublicId: http://znwc.cnooc/xcoa/services/WsOaSystemService?wsdl=WsOaSystemService.wsdl; systemId: http://znwc.cnooc/xcoa/services/WsOaSystemService?wsdl=WsOaSystemService.wsdl; lineNumber: 6; columnNumber: 3; The element type "hr" must be terminated by the matching end-tag "</hr>". at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2188) ... 13 more
07-17
Apache CXF 在解析 WSDL 或相关的 XSD、SOAP 消息时依赖 XML 解析器（如 Woodstox 或 JDK 内置的 SAX 解析器），若发现非法结构，则抛出 `SAXParseException` 并导致服务创建失败[^1]。 2. **WSDL 地址访问异常** ...
java xml xsd 验证_java xsd 验证 xml
weixin_33737110的博客
02-12 366
java中做xsd验证xml的例子时发现有异常报出，不知什么原因，各位帮忙看下异常！！！Exceptioninthread"main"org.xml.sax.SAXParseException:src-resolve:Cannotresolvethename'Respon...java中做xsd 验证 xml的例子时发现有异常报出，不知什么原因，各位帮忙看下异常！！！Exception in th...
已解决org.xml.sax.SAXException异常的正确解决方法，亲测有效！！！
小明的Java问道之路
08-12 4599
已解决org.xml.sax.SAXException异常的正确解决方法，亲测有效！！！
springmvc 百万级别数据导入 sax方式
qq_30228639的博客
01-17 522
poi excel 导入 大文件导入 sax方式
org.xml.sax.SAXParseException; systemId:报错解决方案①
热门推荐
young_qin的博客
10-29 2万+
org.xml.sax.SAXParseException; systemId:报错解决方案① 本人是在做JAVAWEB时出现的 这个问题，也就是当你部署一个新的工程时，启动会报错“org.xml.sax.SAXParseException; systemId:XXXXXX” ，当然我用过好多网上的解决方法，例如检查XML首行， 检查端口的问题，删除MANIFEST.MF文件，删除多余的XML语...
org.xml.sax.SAXParseException的错误解决
wolvesqun的专栏
03-06 1万+
org.xml.sax.SAXParseException的错误解决   原因在于：struts.xml少了一句话 <!DOCTYPE struts-config PUBLIC "-//Apache Software Foundation//DTD Struts Configuration 1.1//EN" "http://jakarta.apache.org/struts/dtds/st
org.xml.sax.SAXParseException的错误解决 2020-11-20
牧码人的博客
11-20 7458
2020-11-20 09:11:31,554 ERROR [main] org.mybatis.spring.mapper.MapperFactoryBean MapperFactoryBean.java:82 - Error while adding the mapper ‘interface com.vedeng.im.usersign.domain.mapper.UserSignInfoMapper’ to configuration. org.apache.ibatis.builder.Build
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值