JBoss BRMS provides a sophisticated and powerful business rules engine. The BRMS rules engine allows an organization, among other things, to:
- define rules in single, governed, environment.
- define rules in the domain language (or syntax) of the problem domain.
- declaratively define rules. It allows to define what to do, not how to do it
- individually test rules, outside of any application logic.
- (incrementally) update rules without the need to update and/or restart the application that uses the rules.
- have better performance on rule execution than in traditional application code.
An often asked question is how to effectively and efficiently debug a rule or a set of rules in a declarative rules engine. Because the rules engine uses sophisticated and complex algorithms like ReteOO and PHREAK, one can no longer simply rely on setting a breakpoint on a left-hand-side (LHS) constraint. When someone is used to imperative programming languages, like Java, declarative languages and runtimes need a bit of practice to debug.
In this article we will provide five ways to make debugging of JBoss BRMS rules applications more efficient and effective.
Continue reading “Get it done with these 5 techniques to debug your JBoss BRMS applications”