Sure,
The major issue that puts us off from using activiti altogether:
Modifying and saving an *.activiti file in the designer, will overwrite the corresponding .bpmn20.xml file, so any modifications done to the .bpmn20.xml file done by hand (e.g. adding a "activiti:initiator" attribute to a start event, which currently can not be done through the designer), will be lost.
This is a major setback for us because throughout our project we will have to change our processes quite often (requirements change), also our processes tend to become very sizable, so we can't afford to have all of our xml modifications (which probably coudn't be done using the designer) get overwritten and lost.
There are also some minor nuisances which we can overlook for now:
- Installable only on eclipse SDK (eclipse classic), didn't work on STS or eclipse for java ee (dependency clashes).
- Supported nodes in the palette are not complete. (This could become a major issue halfway through the project.)
I tried to give honest opinions here, tell me whether you also experience the same issues.
Also do you know of any workarounds/tips for these issues?