[jboss-jira] [JBoss JIRA] Commented: (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters

Nikolaj Tørring (JIRA) jira-events at lists.jboss.org
Tue Sep 6 05:06:27 EDT 2011


    [ https://issues.jboss.org/browse/JBRULES-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626352#comment-12626352 ] 

Nikolaj Tørring commented on JBRULES-2934:
------------------------------------------

Why not just use the existing CommandFactoryprovider? E.g.


> 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.CR1
>
>
> 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

       



More information about the jboss-jira mailing list