Andre, Not sure I understand completely the problem you are facing, but it should be straight forward. Can you show us the configuration you are using? For simple unit tests, we have these: https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/drools-c... <https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/drools-c... https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/drools-c... Also here you can see an alternative approach that does not use channels: http://blog.athico.com/2011/01/drools-content-based-routing-with-camel.html Edson <https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/drools-c... 2011/6/9 Andre <morpheusandre(a)web.de&gt; -- Edson Tirelli JBoss Drools Core Development JBoss by Red Hat @ www.jboss.com

Andre, The consequence of a rule is plain java code, so as long as you import the proper classes and use the API correctly, it will work. Although, it seems to me (looking only at the 2 code snippets bellow) that you could probably simplify things if you inserted message bodies instead of the full exchange into the session. My suggestion is for you to define multiple routes and use the session as a dynamic router. Something like this: (using pseudo code) <route> <from uri="activemq:personnel.records"/> <policy ref="droolsPolicy"> ... <to uri="drools:node1/ksession1?action=insertBody"/> ... </policy> </route> <route> <from uri="drools:node1/ksession1?channel=myFile"/> <to uri="file:target/messages/foo"/> </route> <route> <from uri="drools:node1/ksession1?channel=anotherChannel"/> <to uri=.../> </route> rule "Rule 04" dialect "mvel" when $p : Person() then channels["myFile"].send( $p ); end rule "create new person" dialect "mvel" when ... then $neu = new Person(); $neu.firstname = "I"; channels["anotherChannel"].send( $neu ); end Doing it like that, you separate the concerns more clearly. Camel is responsible for all the middleware communication and transport, while your Drools session will deal with the actual routing logic. It also lets your rules to use arbitrary channel names (e.g., "myFile", "anotherChannel") that camel routes will map into actual routes. Finally, all the internals of camel communications (like creating messages, exchanges, etc) are handled transparently for you. That is how I would do it. Hope it helps. Edson 2011/6/10 Andre <morpheusandre(a)web.de&gt; -- Edson Tirelli JBoss Drools Core Development JBoss by Red Hat @ www.jboss.com

is it correct, that the channels only work with an stateful session? why? what is the connection between extracting objects out of drools and the working memory? <drools:grid-node id="node1"/> <drools:kbase id="kbase1" node="node1"> <drools:resources> <drools:resource type="DRL" source="classpath:test.drl"/> </drools:resources> <drools:configuration> <drools:mbeans enabled="true" /> <drools:event-processing-mode mode="STREAM" /> </drools:configuration> </drools:kbase> <drools:ksession id="ksession1" type="stateful" kbase="kbase1" node="node1"> <drools:script> <drools:fire-all-rules/> </drools:script> </drools:ksession> -- View this message in context: http://drools.46999.n3.nabble.com/Drools-Camel-Integration-sending-messag... Sent from the Drools: User forum mailing list archive at Nabble.com.