I (the developer of drools-annotation and drools-spring) don't intend to try. What is need is a real DSL, similar to Jess' but more java-like. I believe that Mark has this planned.

Of course, drools could continue to be configured with spring, but this is quite simple.

http://www-128.ibm.com/developerworks/webservices/library/ws-soa-progmodel9/index.html

• Business Rules and Information Systems:Aligning IT with Business Goals (Addison-Wesley, 2002)
• Business Rules Applied - Building Better Systems Using the Business Rules Approach (Wiley & Sons, 2002)

Not sure if this was helpful in any way; if I talked nonsense someone please set me straight.

1. make drools as service provider, so drools could use for message router or other rule message operation.
2. connector implement drools's RuleBase instance. the RuleBase contains a set of rules for this connector by property's configuration. So one connector for one set of rules.
4. endpoint's property define what kind instance to add drools's assertObject. It could create new instance by class name or instance reference .
5. endpoint's property also define which object instance use as return message payload.
5. At dispatcher's implementation for doSend,doDispach,doReceive: add message payload to drools's assertObject. It also add session, message's properties, endpointURL's properties to drools's assertObject. And then apply rules.

Drools rules will check all those assertObjects and modify them.

For rule base routing, I implement another service provider called "dynamic". Dynamic service provider get at real endpoint URI from message property. Here is the example:

add endpoint URI to message property in Component:
public Object onCall(UMOEventContext context) throws Exception
{
MuleMessage msg = new MuleMessage(obj, context.getMessage());
msg.setProperty("mqadapter_output", "jms://testqueue?connector=queuemanager");
return msg;
}

add endpoint to router and address is the URI property name:

<endpoint address="dynamic:/mqadapter_output"/>

The property also could be list. So it will send message by list of URI.

To create rule base message routing:
1. define new list instance for rdools's assertObject in rule connector.
2. add list to message property.
3. add dynamic endpoint to any router.
4. drools's rules response to add endpoints to list.

Model file:
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE mule-configuration PUBLIC "-//SymphonySoft //DTD mule-configuration XML V1.0//EN"
"http://www.symphonysoft.com/dtds/mule/mule-configuration.dtd">

<mule-configuration id="Logger" version="1.0">

<connector name="LoggerRuleConnector" className="org.mule.providers.rule.RuleConnector">
<properties>
<list name="rules">
<entry value="/org/mule/providers/rule/Logger.drl"/>
</list>
</properties>
</connector>

<model name="Logger">
<mule-descriptor name="Logger"
inboundEndpoint="file:///c:/temp/rule/logger/in"
implementation="org.mule.components.simple.PassThroughComponent">
<outbound-router>
<router className="org.mule.routing.outbound.ChainingRouter">
<endpoint address="rule://test" connector="LoggerRuleConnector"/>
<endpoint address="dynamic://logger_output"/>
</router>
</outbound-router>
</mule-descriptor>
</model>

</mule-configuration>

Rule file:
package org.mule.providers.rule.samples

import org.mule.umo.UMOMessage;

rule "Logger for large file"
no-loop true
when
msg : UMOMessage()
eval(getFileSize(msg) > 10)
then
msg.setProperty("logger_output", "file:///c:/temp/logger/larger?outputPattern=data.txt&outputAppend=true");
modify(msg);
end

rule "Logger for small file"
no-loop true
when
msg : UMOMessage()
eval(getFileSize(msg) <= 10)
then
msg.setProperty("logger_output", "file:///c:/temp/logger/smaller?outputPattern=data.txt&outputAppend=true");
modify(msg);
end

function long getFileSize(UMOMessage msg)
{
byte bytes[] = (byte[])msg.getPayload();
return bytes.length;
}

Well known issue:
1. it does not support receive endpoint.
2. It does not Object filter.
3. It only tests on Drools

There are two example:
1. RuleHello: demo how to use rule for message processing.
2. RuleBaseRounting: demo how to use rule do message rounting. It depends on another feature: "Dynamic service provider". I will request it and post that source codes later

Thanks for the submission. We're going to start looking at this for the next release.

Cheers,

Ross

I've just started importing this. The dependency info is not with the zip. Can you confirm the Jar required. I'm using

drools-3.0.4
drools-jsr94-3.0.4

It also need this dependency -
<dependency>
<groupId>org.jcp</groupId>
<artifactId>jsr94</artifactId>
<version>1.1</version>
</dependency>

I can't find this anywhere, is it in a maven repo somehere, eclse could please attach it.

Same for -

org.apache.jakarta.commons:commons-jci-core:jar:1.0-406301

Thanks,

Ross

For compile, it only needs jsr94-1.1.jar since it does not implement as drools specific.

If you want to run test program: org.mule.test.usecases.providers.rule.RuleSampleTestCase with drools, it needs:
drools-compiler-3.0.4.jar
drools-core-3.0.4.jar
drools-jsr94-3.0.4.jar

With third party library:
antlr-2.7.6.jar
antlr-3.0ea8.jar
commons-jci-core-1.0-406301.jar
commons-jci-eclipse-3.2.0.666.jar
commons-lang-2.1.jar
stringtemplate-2.3b6.jar
xstream-1.1.3.jar

Following libraries are shipped by drools but already in Mule:
commons-collections-3.1.jar
commons-io-1.1.jar
commons--logging-api-1.0.4.jar
jxl-2.4.2.jar
junit-3.8.1.jar
xercesImpl-2.6.2.jar
xml-apis-1.0.b2.jar

Following libraries does not need for test program. It uses for other drools feature like supporting XML rule file, Decision tree.
drools-decisiontables-3.0.4.jar
colt-1.2.0.jar
commons-jci-janino-2.4.3.jar
concurrent-1.3.4.jar
core-3.2.0.666.jar
janino-2.4.3.jar
jung-1.7.2.jar
xpp3-1.1.3.4.O.jar

You can get those files from:
http://labs.jboss.com/portal/jbossrules/downloads

You also need change code in method getRuleInputStream():

from:
return FileUtils.loadResource(fileName, getClass());
to
return new FileInputStream(FileUtils.getResourcePath(fileName, getClass()));

since FileUtils method rename in 1.3.

David Song

To easy get start with drools, you don't have to do any additional setting and just run org.mule.test.usecases.providers.rule.RuleSampleTestCase, see attach file's comment.

David Song

http://svn.codehaus.org/mule-contrib/transports/jsr94-rules

You should committer access to this repo and can build the module using

mvn install

I have uploaded the promised example demostrating the use of Prova and Drools agents on the bus.

Here is a short write-up with a more detailed one to follow.

The key components ProvaUMOImpl.java and DroolsUMOImpl.java are used for sending and (for Prova agents) receiving messages.

There are three parallel conversations ongoing at the same time.

(1) Agent001 sends tow messages to Agent002;
(2) Drools agent notifies Agent002 about a state change;
(3) A more complex scatter-gather protocol for a Manager and two Worker's. The actual code for Worker's is uploaded to the Worker's by the Manager in a mobile-agent fashion.

There is only one rulebase behind each UMO descriptor, which means that if Mule creates several instances, the access from them to the rulebase happens in parallel and in the case of a conversation protocol, should be executed in lock-step. Imagine that an agent expect messages A and then B. If B arrives first due to the thread parallelism, the agent will be in an incorrect state. Lock-step execution always exchanges messages in pairs, i.e., an ack is sent for each message, and then the other side continues.

The formalism behind the agents is based on pi-calculus. It allows for sending and receiving messages in the rule bodies as well as sending agent addresses and conversation-id's as part of each message.

The project uses both Maven 2 and a Maven 2 plugin for Eclipse so it can be run from both.

The examples requires Prova 2.0 Beta 3 that is included in the local Maven repository.

Alex Kozlenkov
Advanced Technology Group
Betfair Ltd.

http://www.mulesource.org/display/DROOLS/Home

http://svn.muleforge.org/mule-transport-drools/trunk/

Alex, looking at the forge project you should be listed as despot as well. If you sign up on the forge I will get someone to add you to the project. There are currently no artifacts because one of the tests fail.