在SAP WAS 7.3上部署Orbeon

时间:2011-07-29 18:15:18

标签: orbeon

我们正在尝试使用SAP WAS上的Web应用程序部署orbeon。目前它在tomcat上运行,orbeon部署为单独的WAR文件,一切正常。在SAP WAS上,我们收到错误消息“找不到页面”,这是由config中的not-found.xhtml生成的。打开登录orbeon后,我们发现了以下差异

Tomcat日志: 2011-07-28 14:40:40,685 DEBUG TeeProcessor - 用于输出id的freed SAXStore:step-url;近似大小:392字节 2011-07-28 14:40:40,685 DEBUG MSVValidationProcessor - http://www.orbeon.org/oxf/xml/url验证在3完成 2011-07-28 14:40:40,692 DEBUG URLGenerator - 读取配置:[oxf:/ops/xforms/xforms-renderer.xpl | null | null | 001 | true | false | false | false | [false | true | false |假|虚假|虚假] 2011-07-28 14:40:40,692 DEBUG ProcessorImpl - Cache [data,class org.orbeon.oxf.processor.validation.MSVValidationProcessor,config,class org.orbeon.oxf.processor.generator.URLGenerator]:key cacheable for key 'InputCacheKey [class:org.orbeon.oxf.processor.generator.URLGenerator,inputName:config,CompoundOutputCacheKey [class:org.orbeon.oxf.processor.validation.MSVValidationProcessor,outputName:data,key:[CompoundOutputCacheKey [class:org。 orbeon.oxf.processor.generator.URLGenerator,outputName:data,key:[SimpleOutputCacheKey [class:org.orbeon.oxf.processor.generator.URLGenerator,outputName:data,key:[oxf:/ org / orbeon / oxf / xml] /schemas/url-generator-config.rng|application/xml|null|000|true|false|false|false | [false | true | false] | false | false | false]]]]],DocKey [SimpleOutputCacheKey [class] :org.orbeon.oxf.processor.generator.DOMGenerator,outputName:data,key:no decorate cfg]],DocKey [SimpleOutputCacheKey [class:org.orbeon.oxf.processor.generator.DOMGenerator,outputNam e:数据,键:内联输入]]]]]'。存储对象:org.orbeon.oxf.processor.generator.URLGenerator$ConfigURIReferences@36fe4e0d 2011-07-28 14:40:40,693 DEBUG URLGenerator - 配置发现:org.orbeon.oxf.processor.generator.URLGenerator$ConfigURIReferences@36fe4e0d 2011-07-28 14:40:40,693 DEBUG URLGenerator - OXF协议:使用ResourceManager获取密钥 /ops/xforms/xforms-renderer.xpl

SAP WAS日志:

2011-07-28 12:27:29,372 [] [] DEBUG [org.orbeon.oxf.processor.generator.URLGenerator]阅读配置:[oxf:/config/not-found.xhtml | null | null | 001 |真|假|虚假|虚假| [假|真|假|虚假|虚假|虚假] 2011-07-28 12:27:29,373 [] [] DEBUG [org.orbeon.oxf.processor.ProcessorImpl] Cache [data,class org.orbeon.oxf.processor.validation.MSVValidationProcessor,config,class org.orbeon。 oxf.processor.generator.URLGenerator]:源可缓存的键'InputCacheKey [class:org.orbeon.oxf.processor.generator.URLGenerator,inputName:config,CompoundOutputCacheKey [class:org.orbeon.oxf.processor.validation.MSVValidationProcessor, outputName:data,key:[CompoundOutputCacheKey [class:org.orbeon.oxf.processor.generator.URLGenerator,outputName:data,key:[SimpleOutputCacheKey [class:org.orbeon.oxf.processor.generator.URLGenerator,outputName:data, key:[oxf:/org/orbeon/oxf/xml/schemas/url-generator-config.rng | application / xml | null | 000 | true | false | false | false | [false | true | false | false | false | false]]]]],DocKey [SimpleOutputCacheKey [类:org.orbeon.oxf.processor.generator.DOMGenerator,outputName:data,key:no decorate cfg]],DocKey [SimpleOutputCacheKey [class:org.orbeon.oxf。 processor.gen erator.DOMGenerator,outputName:data,key:inline input]]]]]'。存储对象:org.orbeon.oxf.processor.generator.URLGenerator$ConfigURIReferences@5a5bc44a 2011-07-28 12:27:29,374 [] [] DEBUG [org.orbeon.oxf.processor.generator.URLGenerator]配置发现:org.orbeon.oxf.processor.generator.URLGenerator$ConfigURIReferences@5a5bc44a 2011-07-28 12:27:29,374 [] [] DEBUG [org.orbeon.oxf.processor.generator.URLGenerator] OXF 协议:使用ResourceManager获取密钥/config/not-found.xhtml 为什么在SAP WAS中调用not-found.xhtml?调用not-found.xtml的条件是什么。可以使用更多日志记录。

XHTML是在我们的Web应用程序中从JSP添加转发进行处理,或者通过过滤器,orbeon doc中建议的标准单独部署。

谢谢,

安德烈

1 个答案:

答案 0 :(得分:0)

最近Orbeon Forms尚未在SAP NetWeaver Application Server上进行过测试,如果不安装您正在使用的特定版本的SAP NetWeaver Application Server,重现问题并追踪问题,则无法确定问题所在。问题。这是一个狭隘的用例,被认为是Orbeon的一个高优先级问题。因此,解决这个问题的最佳方法是:

  1. 使用其他应用程序服务器(例如Tomcat)。
  2. 自己调查问题,因为Orbeon Forms是开源的。
  3. 让您的组织让Orbeon在Development Support subscription下为您执行此操作。