Return-Path: X-Original-To: apmail-uima-user-archive@www.apache.org Delivered-To: apmail-uima-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 77517184FE for ; Thu, 10 Dec 2015 14:16:45 +0000 (UTC) Received: (qmail 66470 invoked by uid 500); 10 Dec 2015 14:16:45 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 66423 invoked by uid 500); 10 Dec 2015 14:16:45 -0000 Mailing-List: contact user-help@uima.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@uima.apache.org Delivered-To: mailing list user@uima.apache.org Received: (qmail 66411 invoked by uid 99); 10 Dec 2015 14:16:44 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Dec 2015 14:16:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 5AB1CC1456 for ; Thu, 10 Dec 2015 14:16:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.129 X-Spam-Level: *** X-Spam-Status: No, score=3.129 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id I1TipxmCqI4F for ; Thu, 10 Dec 2015 14:16:41 +0000 (UTC) Received: from mail-wm0-f52.google.com (mail-wm0-f52.google.com [74.125.82.52]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id A13F5429C4 for ; Thu, 10 Dec 2015 14:16:40 +0000 (UTC) Received: by mail-wm0-f52.google.com with SMTP id u63so25809495wmu.0 for ; Thu, 10 Dec 2015 06:16:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=8pcbCgvzTEvg6rNsLvpvS3zFNaPUAfxtpuPujxaIr3k=; b=o0cUdO7U121OVyvMZta324XsCCHTFvCamIQXZuvYyyu7eyfcrJEzwuu675KGc+VvSj XQuSxwXkANiD4ujbxoZoauC+Hs3PkQssxYBPMw9LYZ5bzb8AGuGoYD+B+DJLqE9e8wyo WZW03xyQJmG8sszjj1lCPxhFC1w2BKcZogXZ59zPvnPRwaI0ZD4KJV4O2ayxF+uCz97M 00JBgV83qC/+b+jSFJbhgmft1dMwi2oIzxF95AP+8Nf27jBCyxFzwAuIdpcdy7TOZfzA pRP80F+q3TU2/xmmdtDIprG4IElMIFqiMgoX7kqZXb811z9SsjovFbsWwkM668XfoD8f 9dOQ== MIME-Version: 1.0 X-Received: by 10.28.96.4 with SMTP id u4mr20024637wmb.52.1449756999729; Thu, 10 Dec 2015 06:16:39 -0800 (PST) Received: by 10.27.12.80 with HTTP; Thu, 10 Dec 2015 06:16:39 -0800 (PST) Date: Thu, 10 Dec 2015 09:16:39 -0500 Message-ID: Subject: uimaFIT auto-detection of types From: Matthew DeAngelis To: user@uima.apache.org Content-Type: multipart/alternative; boundary=001a1148e998fac93105268bda80 --001a1148e998fac93105268bda80 Content-Type: text/plain; charset=UTF-8 Hi all, I am struggling with type auto-detection in Eclipse. Following the documentation (and this document: https://code.google.com/p/uimafit/wiki/TypeDescriptorDetection), I have placed my type system descriptors in desc/types/*.xml (also just desc/*.xml) and created types.txt in META-INF/org.apache.uima.fit with the line classpath*:desc/types/*.xml (I have tried placing the types.txt file in the folder META-INF/org.uimafit as well, following Richard's document above, with the same results). However, I am still getting missing type complaints at runtime. For instance, the following code runs a reader and a single analysis engine, DJNMultiplier, that relies on the typesystem specified in desc/types/DJTypes.xml. CollectionReaderDescription cr = createReaderDescription(...); TypeSystemDescription tsd = TypeSystemDescriptionFactory.createTypeSystemDescription(); AnalysisEngineDescription djread = AnalysisEngineFactory.createEngineDescription(DJNMultiplier.class,tsd); SimplePipeline.runPipeline(cr,djread); This results in: "org.apache.uima.cas.CASRuntimeException: JCas type "document.DJInfo" used in Java code, but was not declared in the XML type descriptor." Changing the code to specify the location of the typesystem runs fine: CollectionReaderDescription cr = createReaderDescription(...); TypeSystemDescription tsd = TypeSystemDescriptionFactory.createTypeSystemDescription("desc/types/DJTypes"); AnalysisEngineDescription djread = AnalysisEngineFactory.createEngineDescription(DJNMultiplier.class,tsd); SimplePipeline.runPipeline(cr,djread); The latter code would actually be fine for most of my needs, except that I am trying to create a jar file following the instructions in the documentation found here: https://uima.apache.org/d/uimafit-current/tools.uimafit.book.html#ugr.tools.uimafit.packaging. These instructions seem predicated on typesystem auto-detection. When I use Maven Shade to build a jar from the latter code, it complains that: "No file with the name "desc/types/DJTypes.xml" was found in the class path or data path". I suppose that a solution to my problem could include a way to package up the typesystem descriptors so that they can be seen within the jar file; I'm not especially picky about getting this thing running. Any help would be appreciated. I am probably missing something basic, but I'll be darned if I can see it. Regards, Matt --001a1148e998fac93105268bda80--