Yes it's there:
public interface WorkItem {
int PENDING = 0;
int ACTIVE = 1;
int COMPLETED = 2;
int ABORTED = 3;
depending on your work item handler implementation you will set the state as
you wish.. notice that you can add more states if you need a complex life
cycle. That means that it's not fixed to one single state when it's active.
You can implement multiple phases of execution.
On Fri, Apr 2, 2010 at 7:24 PM, tolitius <webakaunt(a)gmail.com> wrote:
not sure where you are going with this, but ok:
public interface ProcessInstance extends EventListener {
int STATE_PENDING = 0;
int STATE_ACTIVE = 1;
int STATE_COMPLETED = 2;
int STATE_ABORTED = 3;
int STATE_SUSPENDED = 4; // <<<<<<<<<<<
//....
}
So does WorkItem:
public class WorkItemImpl implements WorkItem, Serializable {
private static final long serialVersionUID = 400L;
private long id;
private String name;
private int state = 0; //
<<<<<<<<<<<<<<<<<<<<<<<<<<
private Map<String, Object> parameters = new HashMap<String,
Object>();
private Map<String, Object> results = new HashMap<String, Object>();
private long processInstanceId;
// ....
}
And yes, it is framework concern from both angles.
/Anatoly
--
View this message in context:
http://n3.nabble.com/Resuming-the-Flow-SESSION-ID-PROCESS-INSTANCE-ID-WOR...
Sent from the Drools - User mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
-
http://salaboy.wordpress.com
-
http://www.jbug.com.ar
- Salatino "Salaboy" Mauricio -