|
|||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Objectorg.jbpm.graph.def.GraphElement
org.jbpm.graph.def.Node
org.jbpm.graph.node.Merge
public class Merge
TODO is the merge node usefull ? i don't think the merge node is usefull because every node has an implicit merge in front of it (= multiple transitions can arrive in the same node). maybe we should just leave this in for the sake of workflow patterns ?
Field Summary |
---|
Fields inherited from class org.jbpm.graph.def.Node |
---|
action, arrivingTransitions, isAsync, leavingTransitions, superState, supportedEventTypes |
Fields inherited from class org.jbpm.graph.def.GraphElement |
---|
events, exceptionHandlers, name, processDefinition |
Constructor Summary | |
---|---|
Merge()
|
|
Merge(java.lang.String name)
|
Method Summary | |
---|---|
void |
execute(ExecutionContext executionContext)
override this method to customize the node behaviour. |
boolean |
isSynchronized()
|
void |
setSynchronized(boolean isSynchronized)
|
Methods inherited from class org.jbpm.graph.def.GraphElement |
---|
addEvent, addExceptionHandler, equals, executeAction, findExceptionHandler, fireAndPropagateEvent, fireEvent, getEvent, getEvents, getExceptionHandlers, getId, getName, getParentChain, getParents, hasEvent, hasEvents, raiseException, removeEvent, removeExceptionHandler, reorderExceptionHandler, setProcessDefinition, toString |
Methods inherited from class java.lang.Object |
---|
clone, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait |
Constructor Detail |
---|
public Merge()
public Merge(java.lang.String name)
Method Detail |
---|
public void execute(ExecutionContext executionContext)
Node
execute
in class Node
public boolean isSynchronized()
public void setSynchronized(boolean isSynchronized)
|
|||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |