Hello,
we are using new camel - activiti integration from version 5.12. We have a parent process with a 'activity call' starting a subprocesses .
In a jUnit tests for those subprocesses the camel activiti integration works fine and camelProducerTemplate start the route which eventually call receive task in a process like mentioned in user guide:
from("direct:receive1").to("activiti
ubprocess1:task1");
When we try to use such receive task from a jUnit test which is testing the parent process, it does not work, saying that route was not found.
By intuition something llike this should work but it does not:
from("direct:receive1").to("activiti
arentProcessubprocess1:task1");
we are using new camel - activiti integration from version 5.12. We have a parent process with a 'activity call' starting a subprocesses .
In a jUnit tests for those subprocesses the camel activiti integration works fine and camelProducerTemplate start the route which eventually call receive task in a process like mentioned in user guide:
from("direct:receive1").to("activiti
ubprocess1:task1");When we try to use such receive task from a jUnit test which is testing the parent process, it does not work, saying that route was not found.
By intuition something llike this should work but it does not:
from("direct:receive1").to("activiti
arentProcessubprocess1:task1");
Actually it seems that your endpoint name has one more extra parent. It should be simply:
activitirocessName or activitirocessName:servicename
activiti
rocessName or activitirocessName:servicename
