As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
ProcessInstance instance = runtimeService.startProcessInstanceByKey(processKey);
It's important to note that the Activiti engine will continue process execution steps until it reaches a wait state, such as the user task. At such a wait state, the current state of the process instance is stored in the database. It remains in that state until a user decides to complete its task. At that point, the engine will continue until it reaches a new wait state or the end of the process. When the engine reboots or crashes in the meantime, the state of the process is safe and well in the database.
But could i do something for having it directly after the instance launch because i need it before the instance reaches the first javaservice task.
Maybe this should be mentioned very early in the docs…
If i put "async = true" then it doesn t find my class "com.test.ActivitiTask" and doesn t lauch my method execute…
Maybe this should be mentioned very early in the docs…I don't know … async is a pretty complex thing to grasp … Definitely if you don't understand the regular transactional way of execution …
Other question :Could it be possible that, because i'm deploying my xml on activiti-explorer, when i lauch the process instance and engine in my application (not activiti explorer), activiti try to search my class (in the async javaservicetask) in activiti-explorer evenif i really don't think so (logically, it would search, as you said, in the same JVM)