We have a production system using activiti to manage our processes. Up to now we have only included service tasks, deferring work on user tasks until now.
I have a good understanding of how user tasks work and how to implement them. However, I have run into a problem and I am looking for any advice or comments on my conclusions.
We do not deploy our activiti engine to tomcat, opting instead to deploy it embedded in our standalone application. This works very well for us. Now when I try to add a UserTask I have issues when trying to link it to activiti explorer. It seems that even though the activiti explorer and our application share the same database I need to actually deploy my application into activiti explorer for UserTask to work correctly.
This is not a good model for us so I have come up with the following:
1. Created standard ServiceTask types that write information to a queue
2. An external UI will monitor this queue and pull the information, displaying it to an end user.
3. The user submits from the UI, putting a response message on another queue
4. A ReceiveTask picks up from this response queue.
So essentially I am mimicking the idea of a UserTask and avoiding the need to tomcat to be my deployment engine.