The notion of having "application-data" objects is useful, so I don't
have to define lookup tables as parameters in every rule.  However, it
seems like a missing element is the ability to define initialization
code for application-data (or whatever).  This code should run before
any of the rules in a ruleset fire.

Obviously, I can execute this initialization code in my Java code that
parses the rulebase, but it's likely that some of that initialization
code might be considered "business logic".  For instance, defining
lookup table entries.

Unless I've missed something, there isn't a "clean" way to do this out
of the box.  Would this be a worthwhile enhancement to consider?

Reply via email to