Book Image

Mastering JBoss Drools 6

By : Mariano De Maio, Mauricio Salatino, Esteban Aliverti
Book Image

Mastering JBoss Drools 6

By: Mariano De Maio, Mauricio Salatino, Esteban Aliverti

Overview of this book

Mastering JBoss Drools 6 will provide you with the knowledge to develop applications involving complex scenarios. You will learn how to use KIE modules to create and execute Business Rules, and how the PHREAK algorithm internally works to drive the Rule Engine decisions. This book will also cover the relationship between Drools and jBPM, which allows you to enrich your applications by using Business Processes. You will be briefly introduced to the concept of complex event processing (Drools CEP) where you will learn how to aggregate and correlate your data based on temporal conditions. You will also learn how to define rules using domain-specific languages, such as spreadsheets, database entries, PMML, and more. Towards the end, this book will take you through the integration of Drools with the Spring and Camel frameworks for more complex applications.
Table of Contents (18 chapters)
Mastering JBoss Drools 6
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface
Index

Reporting a bug in Drools


Despite being a mature framework, Drools is not immune to bugs of course. When a bug is found, the best thing we can do as a Drools' user is report it. Drools' issues are tracked in the following web application: https://issues.jboss.org/projects/DROOLS

Before reporting an issue, we should always do some research and check whether the issue is not already reported. If we are dealing with an unreported issue, the best way to make it attractive to the Drools' team—and probably increasing the chances to be resolved—is to provide a complete description of the problem along with a self-contained Maven project, exposing the issue in one or more unit tests. Self-contained tests can also be submitted via pull-requests to the Drools GitHub repository at https://github.com/droolsjbpm/drools.

Once the issue is created, we can keep a track of it either in the issue tracker application or by joining the #drools channel on www.freenode.net IRC and politely asking the team if they...