From user-return-4901-apmail-uima-user-archive=uima.apache.org@uima.apache.org Tue Apr 30 08:48:58 2013 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 D39FE10735 for ; Tue, 30 Apr 2013 08:48:58 +0000 (UTC) Received: (qmail 98297 invoked by uid 500); 30 Apr 2013 08:48:58 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 98158 invoked by uid 500); 30 Apr 2013 08:48:58 -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 98145 invoked by uid 99); 30 Apr 2013 08:48:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Apr 2013 08:48:57 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_PASS,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [77.87.224.108] (HELO m4-bln.bund.de) (77.87.224.108) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Apr 2013 08:48:52 +0000 Received: from m4.mfw.bln.ivbb.bund.de (localhost.mfw.bln.ivbb.bund.de [127.0.0.1]) by m4-bln.bund.de (8.14.3/8.14.3) with ESMTP id r3U8mULZ014333 for ; Tue, 30 Apr 2013 10:48:30 +0200 (CEST) Received: (from localhost) by m4.mfw.bln.ivbb.bund.de (MSCAN) id 6/m4.mfw.bln.ivbb.bund.de/smtp-gw/mscan; Tue Apr 30 10:48:30 2013 X-P350-Id: 0bfc2ab8f5602ee4 From: To: Subject: AW: uimaFit way of creating an analysis description from an XML descriptor file Thread-Topic: uimaFit way of creating an analysis description from an XML descriptor file Thread-Index: Ac5E6ubZ89i2Xu7sSnSVp6aVTEFlF///8vcA//7LnIA= Date: Tue, 30 Apr 2013 08:48:22 +0000 Message-ID: References: In-Reply-To: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [126.25.25.118] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Hi Richard, I'm not talking about type system descriptors, but of analysis engine descr= iptors. I would like to create an AnalysisEngineDescription from an analysi= s engine descriptor file, e. g. like one the Textmarker Workbench created i= n a Textmarker Eclipse project. I'd like to add this AnalysisEngineDescript= ion to AggregateBuilder and run the aggregate with SimplePipeline.run(). So= I can mix Textmarker ae with my own. Cheers, Armin =20 -----Urspr=FCngliche Nachricht----- Von: Richard Eckart de Castilho [mailto:richard.eckart@gmail.com]=20 Gesendet: Montag, 29. April 2013 18:18 An: user@uima.apache.org Betreff: Re: uimaFit way of creating an analysis description from an XML de= scriptor file Hi Armin, the equivalent to your code would be something like TypeSystemDescriptionFactory.createTypeSystemDescriptionFromPath("/some/pat= h/AnalysisEngineDescriptorFile.xml") However, I'd usually prefer to store my type system descriptors as a resour= ce in my projects, so that they end up in JARs and on the classpath. To imp= ort one type system in another, I use "import by name" instead of "import b= y location". Type systems accessible via the classpath can be made known to uimaFIT, so = that you don't actually have to load them manually. Many of the uimaFIT fac= tory methods, like AEF.createPrimitive() exist in a variant that doesn't ta= ke a type system. In these variants, the type system is loaded automaticall= y by uimaFIT. For details see [1]. Hope this helps. Cheers, -- Richard [1] https://code.google.com/p/uimafit/wiki/TypeDescriptorDetection=20 Am 29.04.2013 um 17:04 schrieb : > Hi! >=20 > In classical UIMA you use following code to create an AnalysisEngineDescr= iption from an XML descriptor file. >=20 > final Path descriptorFilePath =3D Paths.get("/some/path/",=20 > "AnalysisEngineDescriptorFile.xml"); > final XMLInputSource xmlInputSource =3D new=20 > XMLInputSource(descriptorFilePath.toFile()); > final AnalysisEngineDescription analysisEngineDescription =3D=20 > UIMAFramework.getXMLParser().parseAnalysisEngineDescription(xmlInputSo > urce); >=20 > Now you can use analysisEngineDescription with org.uimafit.factory.Aggreg= ateBuilder to create an aggregate analysis engine and run the pipeline with= SimpePipeline.run(). >=20 > How is the uimaFit way to do this? >=20 > Cheers, >=20 > Armin >=20 >=20