THSERVERSIDE sent an article at 3.10: Velocity: a Template Engine, Rule Engine, or Both (http://www.theserverside.com/news/thread.tss?thread_id=32467)
The author describes how to use Velocity as Rule Engine to implement the rule decision. As a result, netizens attached to the netizens. And provide better scenario: http://java-source.net/open-source/rule-engines
User Peter Lin (Chinese?) Think once Velocity uses Velocity as Rule Engine, when the system changes (see below), it will face two problems that can be measured and run. 1. Growth of the number of rules 2. The number of conditions included in each rule is 3. the complexity of the rules. The number of objects introduced in the rules itself. (Measured by the number of objects a rule involves) 4. The complexity caused by the object properties. (Complexity of the Rule As Object Attributes Are Compared to Each Other. In Others) 5. Selective Firing of Rules and Grouping of Rules6. Resolution of Potential Comflicts
Each netizen is more discussed in this program.
Look at TSS every day, I feel that the discussion after the article is often very exciting! Very fun.
