Package org.jbpm.pvm.internal.model

default implementation of process execution in ExecutionImpl based on org.jbpm.pvm.internal.model.AtomicOperations Bidirectional relations In this process model thoughout the pvm codebase, there are several bidirectional relations.

See:
Description

Interface Summary

CompositeElement	activity container base class for OpenProcessDefinition and Activity.
Condition	user code that reflects a runtime calculation of a boolean value.
ExecutionKeyGenerator
ObservableElement	a super class for process elements that have events.
OpenProcessDefinition	a graph (or tree) structure that can be executed.

Class Summary

ActivityCoordinatesImpl
ActivityImpl
CompositeElementImpl
EventImpl
EventListenerReference
ExceptionHandlerImpl
ExceptionHandlerSynchronization
ExecutionImpl
ExpressionCondition
ObservableElementImpl	observable and visible process elements.
ProcessDefinitionImpl
ProcessElementImpl	superclass for ActivityImpl, TransitionImpl and ProcessDefinitionImpl.
ProcessModificationsImpl
ProcessModificationsImpl.AddedAction
ProcessModificationsImpl.AddedActivity
ProcessModificationsImpl.AddedTransition
ScopeElementImpl
ScopeInstanceImpl
TimerDefinitionImpl
TransitionImpl
VariableDefinitionImpl	a declaration of a variable.
VariableOutDefinitionImpl
VariableOutDefinitionSet
WireProperties

Enum Summary

Continuation
ExecutionImpl.Propagation

Package org.jbpm.pvm.internal.model Description

default implementation of process execution in ExecutionImpl based on org.jbpm.pvm.internal.model.AtomicOperations

Bidirectional relations

In this process model thoughout the pvm codebase, there are several bidirectional relations. By convention, the bidirectional relations are maintained on the many side. This means that when you call for example CompositeElementImpl.addActivity(org.jbpm.pvm.internal.model.ActivityImpl), that method will also update the inverse pointer by invoking the ProcessElementImpl.setProcessDefinition(org.jbpm.pvm.internal.model.ProcessDefinitionImpl) setter. Setter methods will be plain setter methods and they will NOT update the inverse reference. (that would cause an infinite loop).

In the same spirit, there is the convention that the many side of bidirection relations provide factory methods for the related objects. Those factory methods will also establish the bidirectional relation. E.g. CompositeElementImpl.createActivity(String).