2010-09-23 74 views
0

我正在尝试将我的战争部署到GlassFish(在JBoss中正常工作)。 GlassFish无法使用此消息进行部署。GlassFish部署从元素'url-pattern'开始找到无效内容

[#| 2010-09-23T15:49:00.609-0400 | SEVERE | glassfish3.0.1 | javax.enterprise.system.tools.deployment.org.glassfish.deployment.common | _ThreadID = 24; _ThreadName = Thread -1; | DPL8015:存档中的部署描述符文件WEB-INF/web.xml中的无效部署描述符[erdas-apollo.war]。 第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 | SEVERE | glassfish3.0.1 | javax.enterprise.system.tools.deployment.org.glassfish.deployment.common | _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 | SEVERE | glassfish3.0.1 | javax.enterprise.system.core.com.sun.enterprise.v3.server | _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}'之一。 at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:170) at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:79) at com.sun。 enterprise.v3.server.ApplicationLifecycle.loadDeployer(ApplicationLifecycle.java:612) at com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainerInfos(ApplicationLifecycle.java:554) at com.sun.enterprise.v3.server。 ApplicationLifecycle.deploy(ApplicationLifecycle.java:262) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java: 272) at com.sun.enterprise.v3.admin.CommandRunnerImpl $ 1.execute(CommandRunnerImpl.java:305) at co m.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176) at com.sun.enterprise。 v3.admin.CommandRunnerImpl.access $ 900(CommandRunnerImpl.java:83) at com.sun.enterprise.v3.admin.CommandRunnerImpl $ ExecutionContext.execute(CommandRunnerImpl.java:1235) at com.sun.enterprise.v3.admin .CommandRunnerImpl $ ExecutionContext.execute(CommandRunnerImpl.java:1224) at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:365) at com.sun.enterprise.v3.admin.AdminAdapter.service (AdminAdapter.java:204) at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:166) at com.sun.enterprise.v3.server.HK2Dispatcher.dispa第(HK2Dispatcher.java:100) 在com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:245) 在com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java: 791) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954) at com.sun.grizzly。 http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170) 在com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135) 在com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102) 在com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88) at com.sun.grizzly.http.HttpProtocolChain。执行(HttpProtocolChain.java:76) at com。sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57) at com.sun.grizzly.ContextTask.run(ContextTask.java:69) at com.sun.grizzly.util.AbstractThreadPool $ Worker.doWork(AbstractThreadPool.java:330) at com.sun.grizzly.util.AbstractThreadPool $ Worker.run(AbstractThreadPool.java:309) at java.lang。 Thread.run(Thread.java:619) 引起:org.xml.sax.SAXParseException:cvc-complex-type.2.4.a:发现无效的内容以元素'url-pattern'开始。预计会有'{“http://java.sun.com/xml/ns/j2ee":dispatcher}'之一。 at com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read(DeploymentDescriptorFile.java:304) at com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read(DeploymentDescriptorFile.java:225) at com.sun。 enterprise.deployment.archivist.Archivist.readStandardDeploymentDescriptor(Archivist.java:614) at com.sun.enterprise.deployment.archivist.Archivist.readDeploymentDescriptors(Archivist.java:366) at 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.Archivist.open(档案保管员。 java:208) at com.sun.enterprise.deployment.archivist.ApplicationFactory.openArchive(ApplicationFactory.java:148) 在org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:162) ... 31更 引起:org.xml.sax.SAXParseException:CVC-复type.2.4.a:元素'url-pattern'开始找到无效的内容。预计会有'{“http://java.sun.com/xml/ns/j2ee":dispatcher}'之一。 在com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java: 131) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter。 java:318) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator $ XSIErrorReporter.reportError(XMLSchemaValidator.java:417) at com.sun.org.apache.xerces.internal.impl。 xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3181) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:1805) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:705) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl。 java:400) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl $ FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2755) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl。 (XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl。 XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Co nfiguration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser。解析(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp。 SAXParserImpl $ JAXPSAXParser.parse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at 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> 

回答

0

看起来你可能在web.xml文件是无效的条目。

你有一个具有类似过滤器的定义:

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

这将是一个非法入境可能产生读起来就像你所看到的一个错误。

+0

我已经删除了文档中的所有url模式。这些模式在JBoss中运行良好。 – Drew 2010-09-24 19:20:58

+0

@Drew ...你还在坚持吗?你有没有把你的问题的焦点从“帮助我通过这个SAXParseException”改变为“为什么我的原始应用程序在部署到JBoss上时工作” – vkraemer 2010-09-28 15:59:42

+0

不是真的,因为没有关于为什么应用程序可以在JBoss中工作但不是GlassFish 。追查web.xml错误似乎更有用,并可能导致JBoss正常失败的编码错误。 – Drew 2010-09-28 17:01:43

相关问题