In my test, I posted the set-global command along with the rule execution
commands, like this (snippet):
List commands = new ArrayListCommand();
commands.add(CommandFactory.newSetGlobal(logger, logger));
commands.add(CommandFactory.newInsert(fact, outId));
you'd do something like this... in your Java code, instantiate an instance
of your logger (of whatever class)
import org.apache.commons.Log; // or whatever logger class you are using
private Log mylogger = new Log();
then create your command list and add the logger instance as a global:
Could you really compile that rule with return($step) as its last
statment? Rule bodies result in void methods, so...
Anyway, you'll need to provide an out identifier with the insert command
to get the inserted object back in your results:
insert out-identifier=TheFirstStep
The CommandFactory
I added that return($step) in my series of attempts to get the stuff to work
- I don't normally use that statement. It did not change the rule
behaviour. But yes, it did compile (I'm at 5.2 Final).
--
View this message in context:
I am new to calling Rest services and using drools-server. I configured the
camel-server.xml and knowledge-services.xml rest service to use xstream
marshalling, added my rules and pojo model to the war, and deployed it on
tomcat. I wrote a java http client to run the rest service. This is the
also realized i missed a bit of the command xml when i pasted it above. at
the top should be:
batch-execution lookup=workflowKnowledgeSession
--
View this message in context:
http://drools.46999.n3.nabble.com/drools-server-empty-response-body-tp3192475p3192518.html
Sent from the Drools: User
I'm answering my own questions today... the solution here was that the
insert object command MUST have an outIdentifier or results won't be
returned. it doesn't work to just set the returnObject boolean to true
(true is supposed to be the default). Once I set the outIdentifier when i
created
