At the moment it requires command wrapper objects, which map the object to the method.
This allows batch interactions.
There was some work for more RPC type interactions, i.e. maps camel route only to “insert”
and doesn’t need a command wrapper. But I don’t think that made 6.0.
If you know that all objects in the camel rout and just for insertion, you can add a camel
transformer. The transforms the object into a wrapper command object, wrapping the
original object
http://camel.apache.org/message-translator.html
Mark
On 12 Dec 2013, at 17:50, jordan.brown <jordan.brown(a)rackspace.com> wrote:
Hi,
We're currently testing sending XML/JSON (including a message and drools
commands) through Camel and Drools receiving it (using the documentation
given--Part IV Drools Integration in the Doc), but we're curious if it's
possible to just send a Java Object (e.g., Person Object) through Camel and
have Drools pick it up--whereby the object will be received by drools and
then the actual insert and firing of rules will occur on the other side
(i.e., we wouldn't send the drools commands to Camel).
Out-of-the-box, is this possible? Anybody doing this? As of now, we're
continuing the approach in the Drools documentation (Part IV Drools
Integration).
-Jordan
--
View this message in context:
http://drools.46999.n3.nabble.com/Sending-Java-Objects-Through-Camel-rece...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users