Deployment Weblogic上的BlazeDS部署问题:无法创建用于加载消息传递配置的解析器

Deployment Weblogic上的BlazeDS部署问题:无法创建用于加载消息传递配置的解析器,deployment,weblogic,blazeds,Deployment,Weblogic,Blazeds,我正在将一个项目从JBoss迁移到Weblogic服务器。 Java项目使用BlazeDS与Flex前端通信。 它在JBoss上运行良好。然而,我已经挣扎了几天,除了以下例外 flex.messaging.LocalizedException: Unable to create a parser to load messaging configuration. 整个堆栈跟踪: flex.messaging.LocalizedException: Unable to create a parse

我正在将一个项目从JBoss迁移到Weblogic服务器。 Java项目使用BlazeDS与Flex前端通信。 它在JBoss上运行良好。然而,我已经挣扎了几天,除了以下例外

flex.messaging.LocalizedException: Unable to create a parser to load messaging configuration.
整个堆栈跟踪:

flex.messaging.LocalizedException: Unable to create a parser to load messaging configuration.
    at flex.messaging.config.FlexConfigurationManager.getMessagingConfiguration(FlexConfigurationManager.java:73)
    at flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:109)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:299)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:250)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
    at weblogic.servlet.internal.StubSecurityHelper.initServletInstance(StubSecurityHelper.java:94)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:82)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:74)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:60)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:34)
    at weblogic.servlet.internal.ServletStubImpl.initStubLifecycleHelper(ServletStubImpl.java:624)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:565)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1874)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1848)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1738)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2740)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1704)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:781)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:213)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:208)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:70)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:212)
    at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:111)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:213)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:208)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:70)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:24)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258)
    at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:582)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:148)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:114)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:335)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
我研究了BlazeDS源代码中有问题的类。 崩溃,因为解析器在第70行为null。 在第68行,它正在调用,不幸的是返回null

看起来此函数无法找到以下解析器之一

flex.messaging.config.ApacheXPathServerConfigurationParser
flex.messaging.config.XPathServerConfigurationParser
请注意,尽管blazeds版本的web链接看起来是3.0.0.544,但我已经下载了此文件的最新源代码,几乎相同。所以我们可以参考一下

如果有人能给我一些提示,我将不胜感激


提前谢谢!;)

我们终于成功了。我们必须纠正一些关于EJB的配置


但问题的主要原因很可能是导入了GWTDev及其底层XMLAPI

看起来messaging-config.xml文件不可解析。你能在IE中查看一下元素是否正常吗?messaging-config.xml文件是可解析的。在IE或Eclipse中查看时没有错误。谢谢你的提议
flex.messaging.config.ApacheXPathServerConfigurationParser
flex.messaging.config.XPathServerConfigurationParser