Daniel,
the code you are showing is one layer removed from the actual
implementation Mauricio has been showing. The call in CommandFactory:
getCommandFactoryProvider() fetches the actual implementation, i.e., a
CommandFactoryServiceImpl object.
HTH
-W
2011/3/29 Seaver, Daniel (GE Healthcare)
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?
That's weird,
I'm looking at the master repository and that's exactly what the
newStartProcess do:
public Command newStartProcess(String processId,
MapString, Object parameters) {
StartProcessCommand startProcess = new StartProcessCommand();
startProcess.setProcessId(processId);
. Take a look at CmdStyleRuleFlowTest.java.
*Dan*
*From:* Mauricio Salatino [mailto:sala...@gmail.com]
*Sent:* Wednesday, March 16, 2011 4:28 PM
*To:* Rules Users List
*Cc:* Seaver, Daniel (GE Healthcare)
*Subject:* Re: [rules-users] Problem with CommandFactory.newStartProcess
in 5.2 M1
