Back to a month-old topic, herewith some more information. Back then I
asked
1) whether others have suggestions for implementing backtracking in
Jess and
2) whether it would be appropriate to make Activation.setInactive()
public.
Thanks again for your replies so far. Anyone who reads al
I think Jonathan Sewall wrote:
>
> 2. I'd ask that jess.Activation.setInactive(boolean) be made public. We
> currently use selective firing of Activation instances from the agenda.
> For that I employ Rete.run(1) to fire one Activation at a time and
> Activation.setInactive() to deactivate tho
Actually, by selecting the activations that you want to fire yourself
makes a rule-engine useless. If you can solve your problem
algorithmically then you don't need a rule-engine. By letting the
rule-engine decide what order to impose on the rule firings you can
dynamically build the search tree. Y
