Return-Path: Delivered-To: apmail-incubator-uima-user-archive@locus.apache.org Received: (qmail 63442 invoked from network); 24 Oct 2007 15:25:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Oct 2007 15:25:07 -0000 Received: (qmail 61588 invoked by uid 500); 24 Oct 2007 15:24:54 -0000 Delivered-To: apmail-incubator-uima-user-archive@incubator.apache.org Received: (qmail 61561 invoked by uid 500); 24 Oct 2007 15:24:54 -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 61552 invoked by uid 99); 24 Oct 2007 15:24:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Oct 2007 08:24:54 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [130.83.174.24] (HELO lnx130.hrz.tu-darmstadt.de) (130.83.174.24) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Oct 2007 15:24:56 +0000 Received: from callisto.tk.informatik.tu-darmstadt.de (callisto.tk.informatik.tu-darmstadt.de [130.83.163.139]) by lnx130.hrz.tu-darmstadt.de (8.13.4/8.12.10) with ESMTP id l9OFOJZw010861 for ; Wed, 24 Oct 2007 17:24:19 +0200 Received: from dyn07.tk.informatik.tu-darmstadt.de ([130.83.163.217]) by callisto.tk.informatik.tu-darmstadt.de with Microsoft SMTPSVC(6.0.3790.3959); Wed, 24 Oct 2007 17:24:18 +0200 Message-ID: <471F63A1.9090103@tk.informatik.tu-darmstadt.de> Date: Wed, 24 Oct 2007 17:24:17 +0200 From: Christof Mueller User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: uima-user@incubator.apache.org Subject: "Global" Parameters for a CPE References: <471CEC8F.3010300@averbis.de> <471EEBB3.2060408@gmx.de> <0DBCCB475CDE864F8F6086D69BFC5D9FF0626E@CALLISTO.ntdom.tk.informatik.tu-darmstadt.de> <471F3F53.3050808@averbis.de> In-Reply-To: <471F3F53.3050808@averbis.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Oct 2007 15:24:18.0990 (UTC) FILETIME=[F2184CE0:01C81651] X-TUD-HRZ-MailScanner: Found to be clean X-TUD-HRZ-MailScanner-SpamCheck: X-MailScanner-From: mueller@tk.informatik.tu-darmstadt.de X-Virus-Checked: Checked by ClamAV on apache.org Hi Philipp, how about defining the folder path as external resource in the CPE descriptor and bind it to reader and consumer? There is a good example for that in the UIMA manual: http://incubator.apache.org/uima/downloads/releaseDocs/2.2.0-incubating/docs/html/references/references.html#ugr.ref.xml.cpe_descriptor.descriptor.resource_manager_configuration Best regards Christof Philipp Daumke wrote: > Hi Torsten, > > I had the same idea and currently do it like that. But if you work > with millions of documents and you want to initialise (or maybe clean > the folder) just at the beginning it's really a hack to write the > folder information in millions of CASes. > > Another idea that I had was whether it's possible to access the > CollectionReaderXML from the CasConsumer automatically. Is there > something like getCPEComponents().getCollectionReader.getMetaData() > which you can call from any CPEComponent? I couldn't find it so far. > > Thanks for your help > Philipp >>>> I want to read some files from a certain directory and >>> write the results >>> >>>> back in the same folder (in a subdirectory, to be more >>> exactly). (How) >>> >>>> can I define parameters that are both accessible in a >>> CollectionReader >>> >>>> and in a Cas Consumer? Or do I have to define the folder parameter >>>> twice, first in the CollectionReaderXML and second in the >>> CasConsumerXML? >>> >>>> Thanks for your help >>>> Philipp >>>> >>> Excellent question. I tried to figure this out from our >>> documentation and couldn't. Anyone? >>> >> >> As a workaround, one could define the parameter in the CollectionReader >> and add a document annotation that holds the path. The consumer then >> reads the path from the document annotation, so it knows where to put >> the results. >> >> -Torsten >> >> >