2011-07-29 37 views
1

我們正試圖在SAP WAS上部署orbeon與我們的Web應用程序。目前它運行在tomcat上,orbeon被部署爲一個單獨的WAR文件,一切正常。在SAP WAS上,我們收到來自config的not-found.xhtml產生的錯誤消息「Page not Found」。在打開orbeon登錄後,我們發現以下區別在SAP WAS 7.3上部署Orbeon

Tomcat日誌: 2011-07-28 14:40:40,685調試TeeProcessor - 用於輸出id的自由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 | false | false | false]] 2011-07-28 14:40:40,692 DEBUG ProcessorImpl - Cache [data ,類org.orbeon.oxf.processor.validation.MSVValidationProcessor,配置,類org.orbeon.oxf.processor.generator.URLGenerator]:源緩存的關鍵'InputCacheKey [類: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 | DocKey [SimpleOutputCacheKey [class:org.orbeon.oxf.processor.generator.DOMGenerator,outputName:data,key:no decorate cfg]],DocKey [SimpleOutputCacheKey [class: org.orbeon.oxf.processor.generator.DOMGenerator,outputName:data,key:inline input]]]]]'。存儲對象:org.[email protected]36fe4e0d 2011-07-28 14:40:40,693 DEBUG URLGenerator - 配置找到:org.[email protected]36fe4e0d 2011-07-28 14:40:40693 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 | true | false | false | false | [false | true | false | false | false | false]] 2011-07-28 12:27:29,373 [] [ ] DEBUG [org.orbeon.oxf.processor.ProcessorImpl] Cache [data,class org.orbeon.oxf.processor.validation.MSVValidationProcessor,config,org.orbeon.oxf.processor.generator.URLGenerator]:source 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,outputN ame:數據,鍵:內聯輸入]]]]]'。存儲對象:org.[email protected]5a5bc44a 2011-07-28 12:27:29,374 [] [] DEBUG [org.orbeon.oxf.processor.generator.URLGenerator]配置找到: org.[email protected]5a5bc44a 2011-07-28 12:27:29,374 [] [] DEBUG [org.orbeon.oxf.processor.generator.URLGenerator] OXF 協議:使用ResourceManager for key /config/not-found.xhtml 爲什麼會在SAP WAS中調用not-found.xhtml?什麼是not-found.xtml被調用的條件。更多日誌記錄可用。

XHTML是在我們的web應用程序中生成的,從JSP添加轉發處理到orbeon,通過過濾器,orbeon文檔中建議的標準單獨部署。

感謝,

安德烈

+0

SAP WAS支持orbeon嗎? – home

回答

0

Orbeon形式沒有的SAP NetWeaver應用程序服務器上測試最近,有沒有辦法告訴是什麼問題,而無需安裝的SAP NetWeaver應用服務器的特定版本您正在使用,重現問題並追蹤問題。這太狹隘的用例被認爲是Orbeon的高優先級問題。因此,處理此問題的最佳方法是:

  1. 使用其他應用程序服務器(例如Tomcat)。
  2. 自己調查問題,因爲Orbeon Forms是開源的,你可以這樣做。
  3. 讓您的組織通過Development Support subscription讓Orbeon爲您做到這一點。