My group has been evaluating rules engines for an upcoming project. After reading Jess In Action, we've decided that Jess is our rules engine of choice. As we looked at various engines, we noticed that many offerings promoted "Rules Repositories." During our evaluation of Jess, we typically bundled our clp files with our main Jar file. This is nice since everything is in one package. However, I can also see how a repository of rules could pay dividends. (Rules could be changed without compiling/building/deploying the application.) How do you manage your rules? Do you bundle the rule sets with the application? Are they stored in a database that the application references? Maybe even using an interface to CVS or Subversion? I realize the way you deploy your rules would largely depend upon your application and problem domain. We primarily work with Insurance/Bank data.
Thanks, Brian Corbin -------------------------------------------------------------------- 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] --------------------------------------------------------------------
