|
From: Steven D. <ste...@gm...> - 2005-03-28 15:00:08
|
Hi Erwin, > I would probably do this by making the search (or filter) algorithm > configurable for the Person flow. That way the calling parent flow can pass > in the algorithm to use. I find that a good way to think about a flow is as > a method: it has input parameters and can return results. So your person > flow would be something like this, when expressed as a method: > > public Person PersonFlow(String action, SearchAlgorithm algorithm) > Does this mean the Manager and Meeting flows have to put a SearchAlgorithm instance in the session (or the model?) before passing control to the Person subflow? Does this require an action-state before the flow-state in the Manager and Meeting flows? Thanks Steven |