Hi Richard,
you're right. I have to use new CASes or views. Or I can use the same CAS and
restrict the analysis engine to a substring. But that would imply having
parameters for the substring's begin and end offsets in the analysis engine:
Oh, wait a minute, wasn't that my original question?
Hello!
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
