5:16 p.m.
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: Mark Proctor
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
7:18 p.m.
New subject: [JBoss JIRA] Assigned: (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
[
https://issues.jboss.org/browse/JBRULES-2934?page=com.atlassian.jira.plug...
]
Mark Proctor reassigned JBRULES-2934:
-------------------------------------
Assignee: Mauricio Salatino (was: Mark Proctor)
Can you get this fixed for this thu?
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,
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
7:20 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
[
https://issues.jboss.org/browse/JBRULES-2934?page=com.atlassian.jira.plug...
]
Mark Proctor updated JBRULES-2934:
----------------------------------
Fix Version/s: 5.2.0.CR1
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.2.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
2:36 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
[
https://issues.jboss.org/browse/JBRULES-2934?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2934:
--------------------------------------
Fix Version/s: 5.2.0.CR2
(was: 5.2.0.CR1)
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.2.0.CR2
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
1 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
[
https://issues.jboss.org/browse/JBRULES-2934?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2934:
--------------------------------------
Fix Version/s: 5.3.0.Beta1
(was: 5.2.0.Final)
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
4:03 p.m.
New subject: [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
6:41 a.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
[
https://issues.jboss.org/browse/JBRULES-2934?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2934:
--------------------------------------
Fix Version/s: 5.3.0.CR1
(was: 5.3.0.Beta1)
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
4:06 a.m.
New subject: [JBoss JIRA] Commented: (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
[
https://issues.jboss.org/browse/JBRULES-2934?page=com.atlassian.jira.plug...
]
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
4:06 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
[
https://issues.jboss.org/browse/JBRULES-2934?page=com.atlassian.jira.plug...
]
Nikolaj Tørring edited comment on JBRULES-2934 at 9/6/11 5:05 AM:
------------------------------------------------------------------
Why not just use the existing CommandFactoryprovider? E.g.
public static Command newStartProcess(String processId,
Map<String, Object> parameters) { return
getCommandFactoryProvider().newStartProcess( processId, parameters ); }
was (Author: n.torring):
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
3:03 a.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
[
https://issues.jboss.org/browse/JBRULES-2934?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2934:
--------------------------------------
Fix Version/s: 5.3.0.Final
(was: 5.3.0.CR1)
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.Final
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
10:01 a.m.
New subject: [JBoss JIRA] (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
[
https://issues.jboss.org/browse/JBRULES-2934?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2934:
--------------------------------------
Fix Version/s: 5.4.0.Beta1
(was: 5.3.0.Final)
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.4.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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:15 a.m.
New subject: [JBoss JIRA] (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
[
https://issues.jboss.org/browse/JBRULES-2934?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2934:
--------------------------------------
Fix Version/s: 5.4.0.Beta2
(was: 5.4.0.Beta1)
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.4.0.Beta2
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:26 a.m.
New subject: [JBoss JIRA] (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
[
https://issues.jboss.org/browse/JBRULES-2934?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2934:
--------------------------------------
Fix Version/s: 5.4.0.Beta3
(was: 5.4.0.Beta2)
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.4.0.Beta3
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:37 a.m.
New subject: [JBoss JIRA] (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
[
https://issues.jboss.org/browse/JBRULES-2934?page=com.atlassian.jira.plug...
]
Toni Rikkola updated JBRULES-2934:
----------------------------------
Fix Version/s: 5.4.0.Final
(was: 5.4.0.CR1)
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.4.0.Final
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:33 a.m.
New subject: [JBoss JIRA] (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
[
https://issues.jboss.org/browse/JBRULES-2934?page=com.atlassian.jira.plug...
]
Mauricio Salatino resolved JBRULES-2934.
----------------------------------------
Resolution: Done
Already fixed in Master and 5.4.x
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.4.0.Final
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4582
days inactive
4973
days old
14 comments
7 participants
participants (7)
-
Dan Seaver (JIRA) -
Geoffrey De Smet (JIRA)
-
Geoffrey De Smet (Updated) (JIRA)
-
Mark Proctor (JIRA)
-
Mauricio Salatino (JIRA)
-
Nikolaj Tørring (JIRA)
-
Toni Rikkola (JIRA)