I've built a prototype based on the drools-server example and thought I'd
post my results here. No questions at this point per se, but I thought I'd
at least send out an update for those interested.


It looks the Drools Camel component produced by JBoss isn't particularly
well suited for routing, although it does simplify configuration a bit.
Ultimately things boil down to:

Command batchCommand = CommandFactory.newBatchExecution(commands,
"ksession1");
ExecutionResults results = template.requestBody("direct:rules",
batchCommand, ExecutionResultImpl.class);


where the route is:

<route>
    <from uri="direct:rules"/>
    <policy ref="droolsPolicy">
        <to uri="drools:node1/ksession1"/>
    </policy>
</route>


This somewhat simplifies the command submission process, but doesn't
necessarily help in performing content based routing (assuming I'm not
missing something). You can insert an Exchange as a fact and get a URI back
as an ExecutionResult value, but this would require message transformation
on either end of the Drools component.


I'm still open to contributing whatever I get working back into the
community, no matter if it's just documenting this process or some code
resulting from this effort. Knowing the scope of what the Drools component
will do, I wanted to see what would be the most helpful to submit. I could
either do:

Documentation on how to do routing with the JBoss component
Create a new Drools component that performs routing without the JBoss
component
Create a method of generic transformation that works in conjunction with the
JBoss component


For now I'll walk down the path of the first option, but let me know if
another option would be more helpful.


Thanks!


deckerego wrote:
> 
> I'll prototype out some examples using JBoss' own implementation and see
> if there's anything I can add. Looking at
> http://lucazamador.wordpress.com/2010/07/20/drools-server-configuration-updated/
> it seems they've pretty much got everything figured out tho.
> 
> Claus Ibsen-2 wrote:
>> 
>> JBoss have done some work to integrate Drools with Camel
>> http://blog.athico.com/2010/07/declarative-rest-services-for-drools.html
>> 
>> Maybe take a peak at that as well?
>> 
> 

-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Any-interest-in-a-Drools-based-dynamic-router-tp3265110p3267709.html
Sent from the Camel Development mailing list archive at Nabble.com.

Reply via email to