For our purposes, we'd likely want to version an entire 'set' of rules (ruleset or more likely: rulebase), so that each set could be tested before deployment as a unit, for the simplicity therein - if there were a significant performance/load/memory difference in applying versions at the rule level rather than, say, rulebase level, we might consider it, but otherwise, there's a simplicity and testability of knowing that there's only one combination to test per version, rather than trying to make sure that each rule has the same condition, or understanding how the conditions interact to result in one 'version' of the rulebase.
On 11/30/06, Michael Neale <[EMAIL PROTECTED]> wrote:
Have talked to a few people about this, so I thought it was worth a write up in the wiki: http://wiki.jboss.org/wiki/Wiki.jsp?page=RulesGrandfather Basically am fishing for ideas of building in grandfather capability into rules declaratively. (ie 2 different versions of the same rule available, used depending on the data). This is related to but seperate from repository based effective dating. Please reply with any thoughts (or put notes on the wiki). Michael.
-- Geoffrey Wiseman
