Ok, I finally got setup to use git and look at the latest drools code.
In that repository, the code for CommandFactory.newStartProcess looks
like this:
public static Command newStartProcess(String processId,
MapString, Object
parameters) {
There appears to be a problem with CommandFactory.newStartProcess in
Drools 5.2 M1. If I do this:
String someString = Some String;
MapString, Object variables = new HashMapString,
Object();
variables.put(someString, someString);
ListCommand?
Yoni,
The way I do this is within the ruleset. I have an initialization rule
that looks something like this:
when
then
drools.getWorkingMemory().startProcess(ruleflow id);
end
By not putting anything in the when clause, the rule gets activated
and put on the agenda first.
Dan
Thanks for the clarification, Mark.
I followed your links to get the latest of the greatest. Happy to see
all those blue circles in the build history. I downloaded:
drools-5.0.0.SNAPSHOT-eclipse-all.zip
drools-5.0.0.SNAPSHOT-guvnor.zip
Then I updated eclipse with the contents of
