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

Configuration


In the following sections we'll go through some configuration of the various layers. This is necessary before we can write some presentation code and deploy the web application.

JPA annotations for domain objects

We'll start with the persistence layer. All objects that are going to be persisted need to be mapped. This includes the Customer, Address, Account, and Loan objects. The validation message objects don't need to be mapped because they are not going to be persisted. Most of the time the default mapping settings will be used. The @Entity annotation will be used to declare that a class should be persistent, and we'll also explicitly specify the table name. Every entity needs an ID. A uuid field of type String will be added to every entity. The @Id annotation will declare that this uuid field is the ID of an entity. The customer's accounts will be mapped with a @OneToMany annotation, which declares that one customer can have many accounts. Let's now look at a mapping of the...