Hmm … so the use of batch execution instead of InsertObjectCommand improved
things. However I have noticed that although rules are activating as expected,
and facts are being inserted, my queries don’t seem to get any results. For
instance with the following code:
Based on a stateless session:
The mean thing is that the code
org.drools.command.CommandFactory
uses the generic interface
org.drools.command.Command
for all commands without specifying the generic parameter with the many
newXyz methods. If it were written well, it would tell you what to
expect from the command execution,
Thanks for that, Wolfgang. I have been working on something else for a few
days, but just switched over to batch execution, and that is giving me some
appropriate results (my tests are passing).
Which leads me to the question ...
Given that Example 3.4.1 in the Drools 5.5.0.Final user guide doe
I think you have to put your insert command into a list
List> cmds = new ArrayList();
and pass this via batch execution
CommandFactory.newBatchExecution( cmds )
-W
On 04/12/2013, Stephen Masters wrote:
> Hi folks,
>
> Can anyone explain how stateless session execution results should work?
>
Hi folks,
Can anyone explain how stateless session execution results should work? Working
through the docs and tracing the code, it’s getting a bit confusing.
Firstly, according to the user manual, one should be able to insert a list of
facts as a Command, and get an instance of ExecutionResult
