We are designing a Java program (multi-threaded) that monitors for critical
system events and would like to possibly use Jess. We can't afford to end
the program whenever the user wants to change the rules. We want to be
sure we don't miss any activations by having to take down the engine,
reload the rules, and start it back up. I am hoping there is a more
reliable way. I am new to Jess and have some questions in this area.
Is it possible to load/modify/delete rules while the rules engine is
running (e.g. after a call to (run-until-halt)) probably by calling
executeCommand at some point? Basically, we want hot-deployment of rules
after the user has edited them from our Java UI. It would appear that this
could be done with Jess' interpretive design with a combination of some
rules, saving and reloading of facts, possibly using the different events,
maybe replace the parser, or even some use of the activation semaphore.
Is this recommended?
Are there any gotchas?
Will modifying rules on the fly be bad for performance? I am assuming the
rete network will be rebuilt.
Is there a recommended way of doing hot deployment?
Is there a better time to modify the rules during execution, say, specific
"idle" times during rules processing?
Thanks in advance,
Jeff
--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify [EMAIL PROTECTED]
--------------------------------------------------------------------
