[jboss-jira] [JBoss JIRA] Commented: (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
[
https://issues.jboss.org/browse/JBRULES-2934?page=com.atlassian.jira.plug...
]
Dan Seaver commented on JBRULES-2934:
-------------------------------------
Can you please enlighten me as to the reason this fix is being pushed off to 5.3? Did the
proposed fix cause problems with unit tests? It seems like a simple bug with a simple
solution, so I'm a bit concerned. My workaround is awkward and I'm not sure how
usable the Command interface is without it.
CommandFactory newStartProcess doesn't set parameters
-----------------------------------------------------
Key: JBRULES-2934
URL: https://issues.jboss.org/browse/JBRULES-2934
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.2.0.M1
Reporter: Dan Seaver
Assignee: Mauricio Salatino
Labels: droolsjbpm,, startProcess,
Fix For: 5.3.0.Beta1
Should be able to set parameter values when starting a process. Current code:
public static Command newStartProcess(String processId,
Map<String, Object> parameters) {
return getCommandFactoryProvider().newStartProcess( processId );
}
proposed code:
public static Command newStartProcess(String processId,
Map<String, Object> parameters) {
StartProcessCommand cmd = new StartProcessCommand(processId);
cmd.setParameters(parameters);
return cmd;
}
Also, I think this issue would go under the droolsjbpm-knowledge component if the JIRA
component list were updated.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira