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 BC28F107B2 for ; Thu, 17 Apr 2014 13:12:21 +0000 (UTC) Received: (qmail 91531 invoked by uid 500); 17 Apr 2014 13:12:20 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 91354 invoked by uid 500); 17 Apr 2014 13:12:19 -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 91183 invoked by uid 99); 17 Apr 2014 13:12:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Apr 2014 13:12:17 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [132.187.3.35] (HELO mailrelay.rz.uni-wuerzburg.de) (132.187.3.35) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Apr 2014 13:12:11 +0000 Received: from virusscan-slb.rz.uni-wuerzburg.de (localhost [127.0.0.1]) by mailrelay-slb.rz.uni-wuerzburg.de (Postfix) with ESMTP id 83B4B773D2 for ; Thu, 17 Apr 2014 15:11:50 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by virusscan-slb.rz.uni-wuerzburg.de (Postfix) with ESMTP id 80C0A773CF for ; Thu, 17 Apr 2014 15:11:50 +0200 (CEST) X-Virus-Scanned: amavisd-new at uni-wuerzburg.de Received: from mailmaster.uni-wuerzburg.de ([10.101.19.1]) by localhost (vmail002.slb.uni-wuerzburg.de [10.101.19.142]) (amavisd-new, port 10225) with ESMTP id hlIwxN2uI5kS for ; Thu, 17 Apr 2014 15:11:50 +0200 (CEST) Received: from [132.187.15.93] (win6093.informatik.uni-wuerzburg.de [132.187.15.93]) by mailmaster.uni-wuerzburg.de (Postfix) with ESMTPSA id 66C49D27F for ; Thu, 17 Apr 2014 15:11:50 +0200 (CEST) Message-ID: <534FD316.6080307@uni-wuerzburg.de> Date: Thu, 17 Apr 2014 15:11:50 +0200 From: =?ISO-8859-1?Q?Peter_Kl=FCgl?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: user@uima.apache.org Subject: Re: Sofa-unaware AEs that create new views in an AAE References: <534FC366.70209@uni-wuerzburg.de> <1ED08ACD-BB28-489B-9A83-8375E089C071@apache.org> In-Reply-To: <1ED08ACD-BB28-489B-9A83-8375E089C071@apache.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Am 17.04.2014 15:02, schrieb Richard Eckart de Castilho: > On 17.04.2014, at 14:04, Peter Kl�gl wrote: > >> Hi, >> >> as I understand the implementation, an AE is sofa aware if it specifies >> input or output views in its capabilities. Let's say it only specifies >> an output view, so it's sofa aware. If it is part of an AAE with sofa >> mapping (one AAE sofa mapped to the default input view of the AE), then >> it get passed the base CAS independently of the sofa mapping. Shouldn't >> it get the view mapped in the AAE? > It should be able to get the mapped views by the mapped names instead > of by whatever original name they have. > What do you mean exactly? It is maybe possible, or it should be possible? Investigating the metadata in the process() method? > I guess you ask whether it should get the defaultView because the > input view is unmapped? It doesn't get the mapped view, but the base view, which is the _InitialView if the AAE uses it. If the AAE uses some arbitrary input view, it gets an empty sofa. > >> I have a simple AE that should just get the mapped sofa as input and >> then should create a new view, which name is given by a parameter. Is >> it correct that I have to introduce another parameter for the input view >> and have to "getView" in the AE? Is there no way to just use the mapped >> sofa? > Well, what do you map it to? The mapping allows you to have a global set > of view names and a set of local view names for each component. E.g. > your component should postulate that it expects the input data in a view > called "INPUT" (hardcoded - no parameter). Then you use a sofa mapping to > map a global view name to the local name "INPUT" on your AE. Hmm, maybe I do not understand you. "INPUT" would be the name of the view that is accessed in the process() method? Do you mean with postulate the capabilities? If the AE should be able to operate on different input views, e.g., because there are several of those AEs in one AAE, then this would lead again to a parameter specifying "INPUT". Peter > -- Richard