Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.
The focus of this chapter is on various integration points of the Drools engine with other systems.
We'll start with discussion of having Drools artifacts (rules and processes) change on their own life cycle that is independent from the application. We'll see how to build and dynamically load Drools artifacts.
We'll look at how to run rules remotely from a lightweight client. A simple client that can talk to a Drools execution server will be written in Ruby.
Finally, we'll cover integration with the Spring Framework and some rule standards will be discussed.
In almost all examples in this book, the Drools artifacts were packaged together with the application. However, rules, processes, and other Drools artifacts often have different life cycles than the applications that use them. These artifacts tend to change more often than the rest of the application. It would be more beneficial if we could build, release, and deploy them separately. In order to achieve this: