Adam Lally wrote:
On 2/28/07, Michael Baessler <[EMAIL PROTECTED]> wrote:
but when having a FlowController plugged in, this section is missing.
Actually it is possible, but not required, to have a <fixedFlow>
section when using a custom FlowController. (I think the CDE supports
this too, but I'm not sure.)
But I wonder why. I think for these flows, the order of the
analysis engines can also be relevant. How does this work currently? I
think the order of the analysis engine definition is used, right?
The reason it's optional is that a custom FlowController often
wouldn't use a fixed ordering of AnalysisEngines - it may make dynamic
flow decisions based on other criteria.
Note that FlowControllers can define configuration parameters just
like AEs can, so whatever information the FlowController needs to make
routing decisions can be provided that way, if it can't be represented
by the <fixedFlow> object.
The ordering of analysis engine definitions can't be used to make flow
decisions. These are put into a HashMap and the ordering is lost
before it gets to the FlowController.
But how does it work when I would like to implement something like a
CapabilityLanguage flow we already have as build-in
flow. When I implement this a custom flow I would like to specify the
possible order of analysis engines. The custom flow can now decide if
all the engines are called but if, please use the order I have
specified. So I think in this case, it is not a fixed flow that a use
will specify for the custom flow.
-- Michael
