JFDI a new Business Action Scripting Language

We are working on a new non-imperative conseqeuence language for JBoss Ruless, called JFDI which is a sort of business action scripting language. We have placed this project over at Codehaus as we are hoping that it will get taken up by other declarative systems, whether they are rule or process engines. When we firstRead more β†’

Just say no to DynaBeans

The subject of DynaBeans just came up on the mailing list, and it is one I’ve been asked about before – so I thought I would do a blog my answer. Dynabeans was written as a solution for Struts back in 2000, they are not JavaBean compliant – thus they have no value outside ofRead more β†’

Just say no to DynaBeans

The subject of DynaBeans just came up on the mailing list, and it is one I’ve been asked about before – so I thought I would do a blog my answer. Dynabeans was written as a solution for Struts back in 2000, they are not JavaBean compliant – thus they have no value outside ofRead more β†’

Rete with Lazy Joins

I’ve just spent the last four weeks stuck in front jProfiler taking JBoss Rules performance to the next level and the results have been great and well beyond what I hoped. To achieve this I wrote custom collections, unrolled loops and cached variables that are used repeatedly for join attempts. I really feel I’ve takenRead more β†’

Beyond ORM

A rule has many similarities to a query. It contains one or more propositional and first order logic statements organised into a network to filter data additions and changes – we call this a “discrimitation network” as it discrimates against data that does not match its statements. Any data that successfully matches all statements forRead more β†’

JBoss Rules Server

Many people are asking what our plans are for a Rules Server – so I thought I would write them up in visio and blog them, for bonus measure I have added some screenshots of the GWT gui that Michael is working on. Post Comment

Why Java code is bad for rules and a declarative alternative

One of the selling features of Drools, and one of the reasons we are often chosen over competitors, has always been the ability to allow the use of Java code in specific parts of rules; expressions and consequences. This makes for a lower learning curve as Java developers can start writing consequences without additional training;Read more β†’

Real World Rule Engines

Here is an excellent article, introduction reproduced below, from our very own mailing list mentor Geoffrey Wiseman:http://www.infoq.com/articles/Rule-Engines For many developers, rule engines are buzzwords, or black boxes on an architectural diagram: something to be feared or admired from afar, but not understood. Coming to terms with this, is one of the catch-22s of technology: It’sRead more β†’

Rule Execution Flow with a Production Rule System

Some times workflow is nothing but a decision tree, a series of questions with yes/no answers to determine a final answer. This can be modelled far better with a Production Rule System, and is already on the Drools road map. For the other situations we can use a specialised implementation of Agenda Groups to modelRead more β†’