-
Notifications
You must be signed in to change notification settings - Fork 39
org.springframework.beans.factory.UnsatisfiedDependencyException:
Error creating bean with name 'workflowInstanceDao' defined in URL
[jar:file:/some/path/nflow-engine-0.2.1-SNAPSHOT.jar!/com/nitorcreations/nflow/engine/internal/dao/WorkflowInstanceDao.class]:
Unsatisfied dependency expressed through constructor argument with index 1 of type [com.nitorcreations.nflow.engine.internal.dao.ExecutorDao]: :
No bean named 'nflowDatabaseInitializer' is defined; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException:
No bean named 'nflowDatabaseInitializer' is defined
This may be caused by missing Spring profile that selects database engine. You should use one of these spring profiles nflow.db.mysql
, nflow.db.postgresql
, nflow.db.oracle
or nflow.db.h2
. E.g use this system property: -Dspring.profiles.active=nflow.db.mysql
.
Set nflow.autostart=false
, e.g use system property -Dnflow.autostart=false
when starting your application.
With this property nFlow instance won't start a dispatcher thread and thus the instance will not process any workflows.
error: cannot find symbol
public enum State implements WorkflowState {
^
symbol: class WorkflowState
location: class MyWorkflow
Use fully qualified class name for io.nflow.engine.workflow.definition.WorkflowState. This seems to be a JDK bug.
Include javax.activation
library. It seems that they are no longer part of the JDK 10.
<dependency>
<groupId>javax.activation</groupId>
<artifactId>activation</artifactId>
<version>1.1.1</version>
</dependency>
Nothing special happens to child workflows, they continue execute normally.
businessId
can be used in for grouping workflow instances that are related to the same business logic entity. It has no effect to nFlow processing and the same value can be used in any number of workflow instances.
externalId
must be unique within workflow instances of the same workflow type. It can be defined to avoid creating more than 1 instance of workflow instances of given type. If externalId
is undefined when creating the workflow instance, nFlow will generate a random value (UUID.randomUUID().toString()
) for it.
Yes.