代码之家 › 专栏 › 技术社区 › Drew

找到以元素“url pattern”开头的GlassFish部署无效内容

glassfish jboss

Drew · 技术社区 · 15 年前

我正试图将我的战争部署到GlassFish(在JBoss中运行良好)。GlassFish无法使用此消息部署。

[#| 2010-09-23T15:49:00.609-0400 |严重| glassfish3.0.1 | javax.enterprise.system.tools.deployment.org.glassfish.deployment.common | u ThreadID=24;_ThreadName=Thread-1;| DPL8015:存档文件[erdas apollo.war]中的部署描述符文件WEB-INF/WEB.xml中的部署描述符无效。第247行第16列——cvc complex type.2.4.a:以元素“url pattern”开头的内容无效。“{”http://java.sun.com/xml/ns/j2ee“:dispatcher}”之一是预期的

[#| 2010-09-23T15:49:00.609-0400 |严重| glassfish3.0.1 | javax.enterprise.system.tools.deployment.org.glassfish.deployment.common | u ThreadID=24;_ThreadName=Thread-1;| DPL8005:部署描述符解析失败:cvc complex type.2.4.a:从元素“url pattern”开始发现无效内容。“{”http://java.sun.com/xml/ns/j2ee“:dispatcher}”之一是预期的

[#| 2010-09-23T15:49:00.610-0400 |严重| glassfish3.0.1 | javax.enterprise.system.core.com.sun.enterprise.v3.server | u ThreadID=24;_ThreadName=Thread-1;|部署应用程序时出现异常 java.io.IOException:org.xml.sax.SAXParseException:cvc complex type.2.4.a:以元素“url pattern”开头的内容无效。需要{“http://java.sun.com/xml/ns/j2ee”:dispatcher}之一。在org.glassfish.javaee.core.deployment.DolProvider.load上(DolProvider.java:170) 在org.glassfish.javaee.core.deployment.DolProvider.load上(DolProvider.java:79) 在com.sun.enterprise.v3.server.ApplicationLifecycle.loadDeployer上(ApplicationLifecycle.java:612) 在com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainerInfos上(ApplicationLifecycle.java:554) 在com.sun.enterprise.v3.server.ApplicationLifecycle.deploy上(ApplicationLifecycle.java:262) 在com.sun.enterprise.v3.server.ApplicationLifecycle.deploy上(ApplicationLifecycle.java:183) 在org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:272) 在com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:305) 在com.sun.enterprise.v3.admin.CommandRunnerImpl.docomman上(CommandRunnerImpl.java:320) 在com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand上(CommandRunnerImpl.java:1176) 访问$900(CommandRunnerImpl.java:83) 在com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235) 在com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1224) 在com.sun.enterprise.v3.admin.AdminAdapter.docomman上(AdminAdapter.java:365) 在com.sun.enterprise.v3.admin.AdminAdapter.service上(AdminAdapter.java:204) 在com.sun.grizzly.tcp.http11.GrizzlyAdapter.service上(GrizzlyAdapter.java:166) 在com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100) 在com.sun.enterprise.v3.services.impl.ContainerMapper.service上(ContainerMapper.java:245) 在com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693) 在com.sun.grizzly.http.ProcessorTask.process上(ProcessorTask.java:954) 在com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170) 在com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter上(DefaultProtocolChain.java:135) 在com.sun.grizzly.DefaultProtocolChain.execute上(DefaultProtocolChain.java:88) 在com.sun.grizzly.http.HttpProtocolChain.execute上(HttpProtocolChain.java:76) 在com.sun.grizzly.ProtocolChainContextTask.doCall上(ProtocolChainContextTask.java:53) 在com.sun.grizzly.SelectionKeyContextTask.call上(SelectionKeyContextTask.java:57) 在com.sun.grizzly.ContextTask.run上(ContextTask.java:69) 在com.sun.grizzly.util.AbstractThreadPool$Worker.doWork上(AbstractThreadPool.java:330) 在com.sun.grizzly.util.AbstractThreadPool$Worker.run上(AbstractThreadPool.java:309) 原因:org.xml.sax.SAXParseException:cvc complex type.2.4.a:找到以元素“url pattern”开头的无效内容。需要{“http://java.sun.com/xml/ns/j2ee”:dispatcher}之一。在com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read(DeploymentDescriptorFile.java:304) 在com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read上(DeploymentDescriptorFile.java:225) 在com.sun.enterprise.deployment.archivist.archivist.readStandardDeploymentDescriptor上(archivist.java:614) 在com.sun.enterprise.deployment.archivist.archivist.readDeploymentDescriptors上(archivist.java:366) 在com.sun.enterprise.deployment.archivist.archivist.open上(archivist.java:238) 在com.sun.enterprise.deployment.archivist.archivist.open(archivist.java:247) 在com.sun.enterprise.deployment.archivist.ApplicationFactory.openArchive上(ApplicationFactory.java:148) 在org.glassfish.javaee.core.deployment.DolProvider.load上(DolProvider.java:162) ... 31个以上在com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException上(ErrorHandlerWrapper.java:195) 在com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error上(ErrorHandlerWrapper.java:131) 在com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384) 在com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318) 在com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError上(XMLSchemaValidator.java:417) 在com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError上(XMLSchemaValidator.java:3181) 在com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStarElement上(XMLSchemaValidator.java:1805) 在com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement上(XMLSchemaValidator.java:705) 在com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement上(XMLNSDocumentScannerImpl.java:400) 在com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2755) 在com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next上(XMLDocumentScannerImpl.java:648) 在com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) 在com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) 在com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse上(XML11Configuration.java:808) 在com.sun.org.apache.xerces.internal.parsers.XMLParser.parse上(XMLParser.java:119) 在com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse上(AbstractSAXParser.java:1205) 在com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse上(SAXParserImpl.java:522) 在com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read(DeploymentDescriptorFile.java:298) ... 39个以上 |#]

我已经对xml模式定义进行了梳理,但不清楚它的瓶颈是什么。

我已经从文档中删除了所有url模式:

163: <url-pattern>/ws/security/authserver</url-pattern>
169: <url-pattern>/vtor/*</url-pattern>
173: <url-pattern>/ap/*</url-pattern>
177: <url-pattern>/cover/*</url-pattern>
181: <url-pattern>/proc/*</url-pattern>
185: <url-pattern>/em/proxy</url-pattern>
189: <url-pattern>/ctent/*</url-pattern>
193: <url-pattern>/sces/*</url-pattern>
197: <url-pattern>/cat/services/*</url-pattern>
201: <url-pattern>/cat/wrs/*</url-pattern>
207: <url-pattern>/em/czs/*</url-pattern>
212: <url-pattern>/em/quartz/*</url-pattern>
217: <url-pattern>/em/masking</url-pattern>
222: <url-pattern>/min/*</url-pattern>
246: <url-pattern>/min/*</url-pattern>
247: <url-pattern>/sces/rpc</url-pattern>
256: <url-pattern>/cover/E/*</url-pattern>
257: <url-pattern>/cat/csw</url-pattern>
262: <url-pattern>/cover/E_PUBLIC</url-pattern>
314: <url-pattern>/cat/*</url-pattern>
318: <url-pattern>/ctent/*</url-pattern>
331: <url-pattern>/cat/csw/*</url-pattern>
335: <url-pattern>/cat/content/*</url-pattern>
339: <url-pattern>/cat/*</url-pattern>
348: <url-pattern>/min/*</url-pattern>

1 回复 | 直到 15 年前

vkraemer 15 年前

web.xml文件中的某个条目可能无效。

您是否有类似于以下内容的筛选器定义:

<filter-name>Foo</filter-name>
<servlet-name>FooServlet</servlet-name>
<url-pattern>BLAHBLAHBLAH</url-pattern>
<dispatcher>FORWARD</dispatcher>

这将是一个非法的条目,可能会产生一个读起来像你看到的错误。