Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Mastering JBoss Drools 6

You're reading from   Mastering JBoss Drools 6 Discover the power of Drools 6 and Business Rules for developing complex scenarios in your applications

Arrow left icon
Product type Paperback
Published in Mar 2016
Publisher Packt
ISBN-13 9781783288625
Length 330 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (3):
Arrow left icon
Mariano De Maio Mariano De Maio
Author Profile Icon Mariano De Maio
Mariano De Maio
 Salatino Salatino
Author Profile Icon Salatino
Salatino
 Aliverti Aliverti
Author Profile Icon Aliverti
Aliverti
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Mastering JBoss Drools 6
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface
1. Rules Declarative Nature FREE CHAPTER 2. Writing and Executing Rules 3. Drools Runtime 4. Improving Our Rule Syntax 5. Understanding KIE Sessions 6. Complex Event Processing 7. Human-Readable Rules 8. Rules' Testing and Troubleshooting 9. Introduction to PHREAK 10. Integrating Rules and Processes 11. Integrating Drools with our Apps Index

Logical insertion of elements


As we've discussed earlier, we should strive to keep our rules simple. To do so, sometimes, we break down a rule into multiple rules, making insertions of new data in the engine to trigger other simple rules. This helps in keeping the rules manageable as simpler rules will be easily understood. Here's a small example of how we can do such a thing:

rule "determine large orders"
    when $o: Order(total > 150)
    then insert(new IsLargeOrder($o));
end

In this way, we won't have to define what we consider a large order more than once. If we want to change this consideration in the future to, let's say, a total larger than 200, we will only have to change it once.

The one consideration that we need to have with this approach is that if the condition that triggered the insertion of IsLargeOrder might stop being true in the future. If some rule or a piece of code changes the order to have a smaller total, the IsLargeOrder object would still be in the working memory...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images