Hi Mariusz
Thanks for the prompt response :-)
Base your input, I like the paint the this possibility. Two major groups
of objects: Application Object and Rule Engine Object. Application will be
responsible for wrapping incoming request variable (facts) and present
itself to a Rule Engine Object. Rule Engine object (pooled) now load Rule(s)
specific to the application (login validation etc).
Q1. But before I can load the new rules, it will wise to clear all
facts and rules? Any performance issue if we keep loading and unloading
facts/rules?
Q2. How feasible would it be if we intend to keep all patterns in a
RBDMS?
Q3. I'm pretty concern with the RHS/response because it can vary from
modifying existing facts, JDBC call, other class call etc. Should calls just
mentioned (calling method from other classes) be part of the Jess script or
part of the Java code? Performance issue with too much external call by
Jess?
Q4. How feasible would it be to store RHS/action in a RBDMS?
Q5. Possible pitfalls?
Thanks!
Regards
Aloysius
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
