OT Rules is a simple open-source (LGPL) rule engine that focuses on execution, validation and business rules composition. One of the main advantages of using OT Rules (or any rule engine) is that you can define business validations and keep them isolated from business logic so you can add, remove, change or compose these rules and new rules in a simple, flexible way without affecting the business logic. "Execute business validations using OT Rules" gives an introductory knowledge of how can OT Rules be used. OT Rules is part of the OpenTranquera Framework, where other projects are also hosted, like Xkins, Providers, Web and PageSpy among others. Message was edited by: joeo@enigmastation.com

Looks nice. Clean, simple and springable :) -S

In my opinion, one of the better feature is that the rules are written in Java language and the configuration is separated from the rules (xml, spring or other Java code). However, in the future, is possible that the rules will be written in some scripting language.

For folks who need the site translated into English... Use the link below: http://translate.google.com/translate?u=http%3A%2F%2Fopentranquera.sourceforge.net%2Ftiki%2Ftiki-index.php%3Fpage%3DRules&langpair=es%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools Cheers

That´s good... But the article is in english!! The rest of the wiki is in spanish because we are from Argentina :)

I took a quick look at CVS. Have you guys benchmarked it and measured how well it scales with 200 and 1000 rules? If the engine is procedural, it will have a hard time handling thousands of objects and 100 rules. It's nice to see the growing interest in rules and rule engines, but OTRules seems too limited to be useful in complex use cases. For a dozen rules and hand full of objects, it probably runs fine. peter lin

OT Rules is not intended to compete with rule engines like Drools, where you can create an intelligent system. OT Rules takes another approach, it is simpler and allows you to encapsulate business validations and compose and reuse them through your system. Using 1000 rules to execute a business validation is not a common scenario, but using in a range of 10-30 is more common and indeed scales well. We've used this engine in some production projects and certainlly helps us in implementing the validations in the business layer, in fact, this appropach helped us to reuse a lot of code and think the validations in an abstract way, allowing to create generic validations and pass parameters through the configuration file, thus reusing the same rule for different validations. Thanks for your feedback. Regards, Guillermo

It seems a usage of Spring instead of a rule engine.