I cannot seem to find the exact reason why creating a standalone webapp instead of bar/jar in activiti-explorer. Can anybody explain me the advantages or the extra's you have when using the activiti engine embedded in your webapp? What are the limitations of the acitivti-explorer?
The advantage is that all your workflows and business processes can be easily managed using it.
Limitations of activiti explorer is that it cannot be used as the front end for your application, it can be used to quickly have a hands on and feel of how the things would work. You may also use it as an admin tool to deploy your bpmn files.
Thank you proesmans & asriharikiran for this topic.
I have also the same confusion
I believe the workflow should be managed in explorer-activiti and the workflow instances can be created from a separate webapp
I have worked in a webapp in which the process engine and the workflow are both embedded in that webapp but i have encountered some problems like : - Any modification on the workflow the webapp should be re-delivered. - The webapp and workflow manager share the same JVM and then the same memory.
Are you aligned with me?
Thanks in advance for sharing your experiences. Best Regards abataleb
That's really up to you / the customer / the kind of processes you have to run. Activiti allows any option: both embedded in the same app, separated, … that's exactly the power of Activiti!
