I am not sure if I exactly understand what you are trying to do, but in a setting with many views and sofa-unaware AEs, we usually use the AggregateBuilder. I found that more convenient than adding multi-view support to AEs that do not really need it.
AggregateBuilder builder = new AggregateBuilder(); builder.add(segmenter, "_InitialView", "View1"); builder.add(segmenter, "_InitialView", "View2"); builder.add(tagger, "_InitialView", "View1"); builder.add(tagger, "_InitialView", "View2"); (where "segmenter" and "tagger" are AEDs configured before this code block) -Torsten > -----Original Message----- > From: Jörn Kottmann [mailto:[email protected]] > Sent: Wednesday, April 03, 2013 5:54 PM > To: [email protected] > Subject: Re: Multi-view CAS and sofa-unaware AE > > On 04/03/2013 05:10 PM, Peter Klügl wrote: > > Yes, but imagine you have a CAS with 10 views and you want to apply a > > primitive sofa-unaware AE on each view. > > > > The easiest solution I found was to write a template AAE descriptor, > > replaced the AE descriptor and sofa name (and mapping), instantiate > > the AAE, call process(), and then repeat that for the next view. > > > > This can get quite ugly, if you have to override parameters and you do > > not know the primitive AE and its parameters. > > No, sorry don't know whats the best practice to handle this, you probably > want to add multi-view support to your AEs. > > Jörn >
