网站地图
  
  高级搜索
  首页   技术论坛   博客 派计划   产品中心   资源中心   银弹在线   商城  





EOS6按手册部署abframe后,登录时报错,请教错误原因。    
#1楼
给作者发送短消息 给作者发送短消息 实名会员 
查看用户其他信息
初级会员

按照普元提供的《ABFRAME 部署文档》的内容,在EOS6 开发版中部署abframe后,登录测试过程中,页面报如下错误:

 页面流: org.gocom.abframe.auth.Login.flow 不存在。(PageFlow: org.gocom.abframe.auth.Login.flow not exist.)

我是按照文档里的步骤操作的,部署过程很顺利,但就是无法正常登录。

请问,这是什么原因造成的?如何解决?

 

Re: EOS6按手册部署abframe后,登录时报错,请教错误原因。    
#2楼
给作者发送短消息 给作者发送短消息 实名会员 
查看用户其他信息
初级会员

控制台异常信息为:

[eos-default][2009-06-30 17:15:24,000][ERROR][com.primeton.runtime.resource.impl.ResourceNotify:344] com.primeton.ext.data.sdo.startup.WSDLModelLoader,load the resource collection 'wsdl' error.
Added resource:
 E:\primeton_6.0\eosserver\working\eos-default\work\user\com.primeton.workflow.web\com\primeton\eos\tag\WFTagComponent.wsdl
 E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.rights\org\gocom\abframe\rights\application\ApplicationManager.wsdl
 E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.rights\org\gocom\abframe\rights\application\FunctionManager.wsdl
 E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.rights\org\gocom\abframe\rights\menu\MenuManager.wsdl
 E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.rights\org\gocom\abframe\rights\menu\MenuRebuild.wsdl
 E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.rights\org\gocom\abframe\rights\menu\OpershortcutManager.wsdl
 E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.rights\org\gocom\abframe\rights\OperatorManager.wsdl
 E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.rights\org\gocom\abframe\rights\RestrictManager.wsdl
 E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.rights\org\gocom\abframe\rights\role\AssignRoleDuty.wsdl
 E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.rights\org\gocom\abframe\rights\role\AssignRoleOperator.wsdl
 E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.rights\org\gocom\abframe\rights\role\AssignRoleOrgan.wsdl
 E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.rights\org\gocom\abframe\rights\role\AssignRolePosition.wsdl
 E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.rights\org\gocom\abframe\rights\role\AssignRoleWorkgroup.wsdl
 E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.rights\org\gocom\abframe\rights\role\RoleManager.wsdl
 E:\primeton_6.0\eosserver\working\eos-default\work\user\com.primeton.workflow.manager.def\com\primeton\workflow\manager\def\processdef.wsdl

com.primeton.ext.xml.parser.ParserException: cannot resolve reference type 'org.gocom.abframe.dataset.privilege#AcApplication'
 at com.primeton.xml.parser.xsd.sdo.mapping.Element.resolve(Element.java:87)
 at com.primeton.xml.parser.xsd.sdo.mapping.ComplexType.resolve(ComplexType.java:73)
 at com.primeton.xml.parser.xsd.sdo.mapping.Schema.resolve(Schema.java:106)
 at com.primeton.xml.parser.xsd.sdo.mapping.Schemas.resolve(Schemas.java:77)
 at com.primeton.data.sdo.impl.helper.XSDHelperImpl.defineWithWSDL(XSDHelperImpl.java:414)
 at com.primeton.ext.data.sdo.startup.WSDLModelLoader.load(WSDLModelLoader.java:127)
 at com.primeton.ext.data.sdo.startup.WSDLModelLoader.doLoad(WSDLModelLoader.java:113)
 at com.primeton.ext.runtime.resource.loader.AbstractBatchModelLoader.load(AbstractBatchModelLoader.java:75)
 at com.primeton.runtime.resource.impl.ResourceNotify.resourceNotify(ResourceNotify.java:316)
 at com.primeton.runtime.resource.impl.ResourceNotify.notifyResource(ResourceNotify.java:177)
 at com.primeton.runtime.resource.impl.ApplicationResourceLoaderManager.loadApplicationResource(ApplicationResourceLoaderManager.java:65)
 at com.primeton.ext.runtime.resource.startup.ResourceLoaderStartUpListener.start(ResourceLoaderStartUpListener.java:60)
 at com.primeton.runtime.core.impl.RuntimeListenerManagerImpl.startListener(RuntimeListenerManagerImpl.java:103)
 at com.primeton.ext.runtime.core.RuntimeManager.start(RuntimeManager.java:112)
 at com.primeton.ext.runtime.core.RuntimeJ2EEHost.contextInitialized(RuntimeJ2EEHost.java:145)
 at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
 at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
 at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:904)
 at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:867)
 at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474)
 at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
 at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
 at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
 at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
 at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
 at org.apache.catalina.core.StandardService.start(StandardService.java:450)
 at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
[BPS Process Server][2009-06-30 17:15:25,140][INFO] Start BPS Process Server !
[BPS Process Server][2009-06-30 17:15:34,921][INFO] BPS Process Server start up in 10781 ms
[eos-default][2009-06-30 17:15:42,265][ERROR][com.primeton.sca.host.impl.EOSSCADomain:97] Generate the contributin 'file:/E:/primeton_6.0/eosserver/working/eos-default/work/user/org.gocom.abframe.rights/' error.
org.apache.tuscany.sca.contribution.service.ContributionRuntimeException: java.io.FileNotFoundException: E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.auth\org\gocom\abframe\dataset\privilege.xsd (系统找不到指定的路径。)
 at org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolver$WSDLLocatorImpl.getImportInputSource(WSDLModelResolver.java:214)
 at com.ibm.wsdl.xml.WSDLReaderImpl.parseImport(Unknown Source)
 at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
 at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
 at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
 at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
 at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
 at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
 at org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolver.loadDefinition(WSDLModelResolver.java:387)
 at org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolver.loadOnDemand(WSDLModelResolver.java:356)
 at org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolver.aggregate(WSDLModelResolver.java:267)
 at org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolver.resolveModel(WSDLModelResolver.java:304)
 at org.apache.tuscany.sca.contribution.resolver.ExtensibleModelResolver.resolveModel(ExtensibleModelResolver.java:167)
 at org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLInterfaceProcessor.resolveWSDLInterface(WSDLInterfaceProcessor.java:203)
 at org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLInterfaceProcessor.resolve(WSDLInterfaceProcessor.java:238)
 at org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLInterfaceProcessor.resolve(WSDLInterfaceProcessor.java:52)
 at org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifactProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifactProcessorExtensionPoint.java:364)
 at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:170)
 at org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.resolveContracts(BaseAssemblyProcessor.java:405)
 at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:869)
 at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:87)
 at org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifactProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifactProcessorExtensionPoint.java:364)
 at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:170)
 at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:164)
 at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:56)
 at org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtifactProcessor.resolve(ExtensibleURLArtifactProcessor.java:106)
 at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processResolvePhase(ContributionServiceImpl.java:534)
 at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:400)
 at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:189)
 at com.primeton.sca.host.impl.EOSSCADomain.buildContribution(EOSSCADomain.java:94)
 at com.primeton.sca.host.impl.EOSSCADomain.addContribution(EOSSCADomain.java:164)
 at com.primeton.ext.sca.host.ScaSystem.addContribution(ScaSystem.java:281)
 at com.primeton.sca.host.impl.SCAResourceLoadListener.load(SCAResourceLoadListener.java:97)
 at com.primeton.runtime.resource.impl.ResourceNotify.notifyResource(ResourceNotify.java:192)
 at com.primeton.runtime.resource.impl.ApplicationResourceLoaderManager.loadApplicationResource(ApplicationResourceLoaderManager.java:65)
 at com.primeton.ext.runtime.resource.startup.ResourceLoaderStartUpListener.start(ResourceLoaderStartUpListener.java:60)
 at com.primeton.runtime.core.impl.RuntimeListenerManagerImpl.startListener(RuntimeListenerManagerImpl.java:103)
 at com.primeton.ext.runtime.core.RuntimeManager.start(RuntimeManager.java:112)
 at com.primeton.ext.runtime.core.RuntimeJ2EEHost.contextInitialized(RuntimeJ2EEHost.java:145)
 at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
 at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
 at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:904)
 at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:867)
 at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474)
 at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
 at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
 at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
 at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
 at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
 at org.apache.catalina.core.StandardService.start(StandardService.java:450)
 at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
Caused by: java.io.FileNotFoundException: E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.auth\org\gocom\abframe\dataset\privilege.xsd (系统找不到指定的路径。)
 at java.io.FileInputStream.open(Native Method)
 at java.io.FileInputStream.<init>(FileInputStream.java:106)
 at java.io.FileInputStream.<init>(FileInputStream.java:66)
 at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
 at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
 at org.apache.tuscany.sca.xsd.xml.XMLDocumentHelper.getInputSource(XMLDocumentHelper.java:139)
 at org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolver$WSDLLocatorImpl.getImportInputSource(WSDLModelResolver.java:212)
 ... 62 more

 

Re: EOS6按手册部署abframe后,登录时报错,请教错误原因。    
#3楼
给作者发送短消息 给作者发送短消息 实名会员 
查看用户其他信息
总分 278 分
财富 336 goCom币
威望 254
排名 第 62 名
段位 新手必读
页面流: org.gocom.abframe.auth.Login.flow 不存在。(PageFlow: org.gocom.abframe.auth.Login.flow not exist.)
说明是此页面流没有部署成功,单独部署一下文件或部署 org.gocom.abframe.auth构件包
 

Re: EOS6按手册部署abframe后,登录时报错,请教错误原因。    
#4楼
给作者发送短消息 给作者发送短消息 实名会员 
查看用户其他信息
初级会员
2楼贴出来的异常问题,已解决。
原因是,我使用的数据库是SQL Server 2000(项目要求)。在导入abframe.zip时,EOS并没有在相应的路径下生成数据实体对应的文件。我将org.gocom.abframe.auth下所有的数据实体重新导入一遍后,上述异常问题就解决了。

至于1楼提出的“页面流: org.gocom.abframe.auth.Login.flow 不存在。(PageFlow: org.gocom.abframe.auth.Login.flow not exist.)
”的问题,依然没有解决。

我按照hanhongyuan说的方法,
第一次,单独部署了org.gocom.abframe.auth下的页面流Login.flowx;
第二次,重新部署了org.gocom.abframe.auth构建包;
第三次,将整个项目重新部署;

但问题还是存在。我检查了EOS6 的 eosserver目录,发现路径E:\primeton_6.0\eosserver\working\eos-default\work\user\org.gocom.abframe.auth\org\gocom\abframe\auth下,的确没有Login.flow。

为什么EOS在编译时没有生成Login.flow?
哪位仁兄在导入abframe时,遇到过这个问题?
 

Re: EOS6按手册部署abframe后,登录时报错,请教错误原因。    
#5楼
给作者发送短消息 给作者发送短消息 实名会员 
查看用户其他信息
初级会员
问题已解决,我在菜单:项目下,取消自动构建,然后点击【清理】,手工编译一下项目,然后再部署一下,就OK了。

只是不知道,导入abframe时,EOS为什么没有自动构建项目。
 

Re: EOS6按手册部署abframe后,登录时报错,请教错误原因。    
#6楼
给作者发送短消息 给作者发送短消息  
查看用户其他信息
总分 20 分
财富 22 goCom币
威望 1
排名 :(
段位 新手必读
一般在导入项目的时候,如果项目过大,容易出现编译问题,需要重新清理后再部署即可解决问题
 

Re: EOS6按手册部署abframe后,登录时报错,请教错误原因。    
#7楼
给作者发送短消息 给作者发送短消息 实名会员 
查看用户其他信息
初级会员
 

Re: EOS6按手册部署abframe后,登录时报错,请教错误原因。    
#8楼
给作者发送短消息 给作者发送短消息  
查看用户其他信息
初级会员
用EOS实现了自己项目上的一些功能。现在想部署一个自己的新项目,不知如何下手。麻烦楼主提供《ABFRAME 部署文档》,邮箱:onlyonewater@126.com。
 




发表回复
账号用户名   密码   登录
内容:url email imgsrc image code quote
范例 Example
bold italic underline linethrough   


 [更多...]