Book Image

Drools JBoss Rules 5.X Developer's Guide

By : Michal Bali
Book Image

Drools JBoss Rules 5.X Developer's Guide

By: Michal Bali

Overview of this book

<p>Writing business rules has always been a challenging task. Business rules tend to change often leading to a maintenance nightmare. This book shows you various ways to code your business rules using Drools, the open source Business Rules Management System.<br /><br />Drools JBoss Rules 5.X Developer's Guide shows various features of the Drools platform by walking the reader through several real-world examples. Each chapter elaborates on different aspects of the Drools platform. The reader will also learn about the inner workings of Drools and its implementation of the Rete algorithm.<br /><br />The book starts with explaining rule basics, then builds on this information by going through various areas like human readable rules, rules for validation, and stateful rules, using examples from the banking domain. A loan approval process example shows the use of the jBPM module. Parts of a banking fraud detection system are implemented with the Drools Fusion module which is the complex event processing part of Drools. Finally, more technical details are shown detailing the inner workings of Drools, the implementation of the ReteOO algorithm, indexing, node sharing, and partitioning.</p>
Table of Contents (22 chapters)
Drools JBoss Rules 5.X Developer's Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Setting Up the Development Environment
Creating Custom Operators
Dependencies of Sample Application
Index

Design


Let's now look in more detail at the individual layers. The following figure also give us an overview of what we'll be implementing in this chapter. Again, from bottom to top, we'll have two repositories: one for persisting customers and one for accounts. The services layer will have our three already defined services: validation, loan approval, and CEP service. These services will be hidden behind a public BankingService, which will act as a mediator between these services. The presentation tier will use this public service to do all its tasks. There will be various controllers, each responsible for some unit of work; for example, CustomerSaveFormController for saving a customer. The presentation tier will also contain a WS-HumanTask client that will be responsible for all communication with the WS-HumanTask server.

Figure 2: Sample application design

In the persistence layer only the customer repository will be normally used. It will persist the whole object graph (customer object...