Jboss 发现以元素';开头的GlassFish部署无效内容;url模式';

Jboss 发现以元素';开头的GlassFish部署无效内容;url模式';,jboss,glassfish,Jboss,Glassfish,我正在尝试将我的war部署到GlassFish(在JBoss中运行良好)。GlassFish无法部署此消息 [#|2010-09-23T15:49:00.609-0400 | SEVERE | glassfish3.0.1 | javax.enterprise.system.tools.deployment.org.glassfish.deployment.common | u ThreadID=24;| u ThreadName=Thread-1;| DPL8015:归档文件[erdas ap

我正在尝试将我的war部署到GlassFish(在JBoss中运行良好)。GlassFish无法部署此消息

[#|2010-09-23T15:49:00.609-0400 | SEVERE | glassfish3.0.1 | javax.enterprise.system.tools.deployment.org.glassfish.deployment.common | u ThreadID=24;| u ThreadName=Thread-1;| DPL8015:归档文件[erdas apollo.war]中部署描述符文件WEB-INF/WEB.xml中的部署描述符无效。 第247行第16列--cvc复杂类型.2.4.a:发现以元素“url模式”开头的无效内容。元素“{”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 | | u ThreadID=24;| u ThreadName=Thread-1;| DPL8005:部署描述符解析失败:cvc复杂类型。2.4.a:发现以元素“url模式”开头的内容无效。其中一个“{”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;| U ThreadName=Thread-1;|部署应用程序时出现异常 java.io.IOException:org.xml.sax.SAXParseException:cvc复杂类型.2.4.a:发现以元素“url模式”开头的无效内容。其中一个“{”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.setupContainerFos(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.docomand(CommandRunnerImpl.java:320) 位于com.sun.enterprise.v3.admin.CommandRunnerImpl.docomand(CommandRunnerImpl.java:1176) 在com.sun.enterprise.v3.admin.CommandRunnerImpl.access$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.docomand(adminapter.java:365) 位于com.sun.enterprise.v3.admin.adminapter.service(adminapter.java:204) 位于com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:166) 位于com.sun.enterprise.v3.server.HK2Dispatcher.dispatcher(HK2Dispatcher.java:100) 位于com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:245) 在com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791) 位于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:102)上 在com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)上 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) 运行(Thread.java:619) 原因:org.xml.sax.SAXParseException:cvc复杂类型.2.4.a:发现以元素“url模式”开头的无效内容。其中一个“{”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.archivist.open(archivist.java:208) 位于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复杂类型.2.4.a:发现以元素“url模式”开头的无效内容。其中一个“{”http://java.sun.com/xml/ns/j2ee应为“:dispatcher}”。 位于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
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>
<filter-name>Foo</filter-name>
<servlet-name>FooServlet</servlet-name>
<url-pattern>BLAHBLAHBLAH</url-pattern>
<dispatcher>FORWARD</dispatcher>