org.camunda.bpm.engine.impl.migration.validation.instance
Class NoActiveTransitionsActivityInstanceValidator

java.lang.Object
  org.camunda.bpm.engine.impl.migration.validation.instance.NoActiveTransitionsActivityInstanceValidator

All Implemented Interfaces:

MigratingActivityInstanceValidator

public class NoActiveTransitionsActivityInstanceValidator
extends Object
implements MigratingActivityInstanceValidator

Constructor Summary

NoActiveTransitionsActivityInstanceValidator()

Method Summary

protected boolean	hasAsyncTransitionInstances(ActivityInstance activityInstance) Workaround for CAM-5609: In general, only async continuations should be represented as TransitionInstances, but due to this bug, completed multi-instances are represented like that as well.
void	validate(MigratingActivityInstance migratingInstance, MigratingProcessInstance migratingProcessInstance, MigratingActivityInstanceValidationReportImpl instanceReport)

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

NoActiveTransitionsActivityInstanceValidator

public NoActiveTransitionsActivityInstanceValidator()

Method Detail

validate

public void validate(MigratingActivityInstance migratingInstance,
                     MigratingProcessInstance migratingProcessInstance,
                     MigratingActivityInstanceValidationReportImpl instanceReport)

Specified by:

validate in interface MigratingActivityInstanceValidator

hasAsyncTransitionInstances

protected boolean hasAsyncTransitionInstances(ActivityInstance activityInstance)

Workaround for CAM-5609: In general, only async continuations should be represented as TransitionInstances, but due to this bug, completed multi-instances are represented like that as well. We tolerate the second case.