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 F331111FBC for ; Wed, 25 Jun 2014 13:39:59 +0000 (UTC) Received: (qmail 26843 invoked by uid 500); 25 Jun 2014 13:39:59 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 26805 invoked by uid 500); 25 Jun 2014 13:39:59 -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 Delivered-To: moderator for user@uima.apache.org Received: (qmail 14261 invoked by uid 99); 25 Jun 2014 10:06:22 -0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Re: Restricting an aggregate engine to a substring or mention From: Richard Eckart de Castilho In-Reply-To: Date: Wed, 25 Jun 2014 12:05:33 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: user@uima.apache.org X-Mailer: Apple Mail (2.1878.2) X-Provags-ID: V02:K0:ZzuS49PovLOvU0gt3NawHVLF+Zj49pa4p6HivQUey5l yNesu9nOkX4UwHhETnpvy4BNbMNyuR6dryWWwLCIJrWdamdyOP 2C/TgpzMuhXWXkULbC9WgU/2t3WLwgw6FXFoJvZfNLGOT3DXQG 4HitU2rBZfRInPRiULKFHLHeCwmUB3GB6V6JnuH0ykwF5d3z3y 68CwytkOH0v6UZne/tgZ4GrprDBnRZweBHXdCir2ig6qKSeKEc nKdwbIpsiUNOou2kwlo6Np8pUcvRR11rmRLtI6wbqypewdYEyS TErJsOrUIatJ4Twd7lFl0q74NU78laNSRlJiMeq6N2GVZ2HobX FEItqrg5F5VOn51JoBX5Ljfl0GkC8Dll64R1GwrHtsOP+OGi9i WkssGpX6GYjcg== X-Virus-Checked: Checked by ClamAV on apache.org Hi Armin, how would you do the last step: telling the nested AE to process only = the mentions of the segment type?=20 As far as I can see, it again boils down to the point that the = SegmentProcessingAE would internally create one or more new CASes or = view, pass those to the nested AE, and then would have to merge the = results produced by the nested AE back into the original CAS. Cheers, -- Richard On 23.06.2014, at 08:53, Armin.Wegner@bka.bund.de wrote: > Hello! >=20 > I've got another maybe not so good idea. Why not pass an aggregate = analysis engine as a parameter? First, build an aggregate analysis = engine the usual way. Second, serialize it to an XML-string. Third, pass = that string to the SegmentProcessingAE as String parameter together with = another parameter denoting the segment types. Fourth, deserialize the = aggregate engine. Last, Iterate over all mentions of the segment type = and process each segment with the aggregate engine. Does this work? >=20 > What do you think? >=20 > Armin