Return-Path: Delivered-To: apmail-incubator-uima-user-archive@minotaur.apache.org Received: (qmail 33540 invoked from network); 23 Jun 2009 20:43:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Jun 2009 20:43:44 -0000 Received: (qmail 16207 invoked by uid 500); 23 Jun 2009 20:43:55 -0000 Delivered-To: apmail-incubator-uima-user-archive@incubator.apache.org Received: (qmail 16151 invoked by uid 500); 23 Jun 2009 20:43:55 -0000 Mailing-List: contact uima-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: uima-user@incubator.apache.org Delivered-To: mailing list uima-user@incubator.apache.org Received: (qmail 16141 invoked by uid 99); 23 Jun 2009 20:43:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jun 2009 20:43:55 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of chengmin.ding@gmail.com designates 209.85.220.223 as permitted sender) Received: from [209.85.220.223] (HELO mail-fx0-f223.google.com) (209.85.220.223) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jun 2009 20:43:47 +0000 Received: by fxm23 with SMTP id 23so157957fxm.12 for ; Tue, 23 Jun 2009 13:43:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=w4HHH4/NoLZbK3ze6v71MOYtwFG9QvpqdAGFicN6K90=; b=pxlimh4mm73qcUZSSF9jus0a/1j4PLywtMgRTCISBB4t54RITq2+91+N1RnYbxPMWz muuJm4veo+o4MouymmnswDdrQLfpiNgYkrgKVUqxqmYUZlzMMBHRneg5NBHLYzKcTZiD zXG3n8ZiGYiWwzelNOJrcdSzrsN7ptTxf3ZLg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=jqb5V1Dh/cvfPRH5wm1TKgxJGTlUzSNEkzwHBKx1CovChmiCPl3PXCzI8LHv4Zivg2 kvzX43aIAqrkTppT+tGaRO+aAoj3rZsoAjasbraQKmhcEZhYHwB64Ov4sBGOdyC7gBMh Erh4wdTRNVoIstD8+Hl4uDPLycDmFOiPytnLw= MIME-Version: 1.0 Received: by 10.204.72.15 with SMTP id k15mr455464bkj.14.1245789805418; Tue, 23 Jun 2009 13:43:25 -0700 (PDT) Date: Tue, 23 Jun 2009 16:43:25 -0400 Message-ID: <6ec63aa40906231343u66bb0816uc301a52b3c0fcc50@mail.gmail.com> Subject: question about InterOP between Apache UIMA and Omnifind Annotators (CAS2JDBC) From: Chengmin Ding To: uima-user@incubator.apache.org Content-Type: multipart/alternative; boundary=001636c5be2dd11951046d0a0a1c X-Virus-Checked: Checked by ClamAV on apache.org --001636c5be2dd11951046d0a0a1c Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello, We have used the UIMA Adapter for IBM annotators and it worked for some of our testing annotators. However, when we tried it on cas2jdbc, we got the following error: We have a CPE pipeline and the CAS2JDBC is the only consumer/engine based on IBM UIMA framework. We are using Apache UIMA 2.2 for the entire pipeline. We were thinking this was caused by missing Omnifind specific annotator which fills out the DocumentAnnotation or the omnifind specific com.ibm.es.tt.DocumentMetaData feature structure (which contains documentid etc features). We then added the base annotator from Omnifind (OF_Tokenization.xml etc) and also wrapped it up with the adapter. But we still got the same error. Our questions are: 1) Is the error indeed caused by missing some Omnifind specific annotator that fills out the DocumentAnnotation feature structure? 2) Is there any way to further isolate the problem via any tools considering we do not have the source code for cas2jdbc? 3) Can the IBM UIMA Adapter be used the same way to wrap regular annotator, aggregated analysis engine and consumers ? 4) Does Apache UIMA have any plan to come up with a CAS2JDBC compatible db consumer? Thanks a lot! ================================================ org.apache.uima.analysis_engine.AnalysisEngineProcessException at com.ibm.uima.adapter.ibm.IBMAnalysisEngineWrapper.processAndOutputNewCASes(Unknown Source) at org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.process(AnalysisEngineImplBase.java:218) at org.apache.uima.collection.impl.cpm.engine.ProcessingUnit.processNext(ProcessingUnit.java:892) at org.apache.uima.collection.impl.cpm.engine.ProcessingUnit.run(ProcessingUnit.java:577) Caused by: com.ibm.uima.analysis_engine.AnalysisEngineProcessException: The common analysis structure cannot be processed. See the previous exception for details. at com.ibm.uima.reference_impl.analysis_engine.compatibility.CasConsumerAdapter.process(CasConsumerAdapter.java:93) at com.ibm.uima.reference_impl.analysis_engine.PrimitiveAnalysisEngine_impl.callAnalysisComponentProcess(PrimitiveAnalysisEngine_impl.java:392) at com.ibm.uima.reference_impl.analysis_engine.PrimitiveAnalysisEngine_impl.processAndOutputNewCASes(PrimitiveAnalysisEngine_impl.java:297) at com.ibm.uima.reference_impl.analysis_engine.AnalysisEngineImplBase.process(AnalysisEngineImplBase.java:218) ... 4 more Caused by: com.ibm.uima.resource.ResourceProcessException: The common analysis structure cannot be processed. See the previous exception for details. at com.ibm.uima.consumer.cas2jdbc.utils.Cas2JdbcLogger.log_PROCESS_CAS__SEVERE(Unknown Source) at com.ibm.uima.consumer.cas2jdbc.Cas2Jdbc.processCas(Unknown Source) at com.ibm.uima.reference_impl.analysis_engine.compatibility.CasConsumerAdapter.process(CasConsumerAdapter.java:89) ... 7 more Caused by: com.ibm.uima.resource.ResourceProcessException: The document's ID cannot be parsed. See the previous exception for details. at com.ibm.uima.consumer.cas2jdbc.utils.Cas2JdbcLogger.log_BAD_DOCID__SEVERE(Unknown Source) at com.ibm.uima.consumer.cas2jdbc.Cas2Jdbc.parseDocID(Unknown Source) ... 9 more Caused by: java.lang.NullPointerException ... 10 more -Chengmin --001636c5be2dd11951046d0a0a1c--