Active events on completed tasks
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-26-2013 12:19 PM
Hi!!
I'm new in Activiti, but I'm having a problem on a single task in my process.
I can't finish a process instance because I have active events belonging to finished execution.
I'm using activiti 5.11 and the activiti designer.
Thank you very much,
David.
I'm new in Activiti, but I'm having a problem on a single task in my process.
I can't finish a process instance because I have active events belonging to finished execution.
I'm using activiti 5.11 and the activiti designer.
Thank you very much,
David.
Labels:
- Labels:
-
Archive
13 REPLIES 13
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-30-2013 09:13 AM
So, there is no way to solve the problem until you fix this?
Another way to do this, without the signals problem?
Thank you very much.
Another way to do this, without the signals problem?
Thank you very much.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-06-2014 07:04 AM
> So, there is no way to solve the problem until you fix this?
No, the problem you stated above is not happening. The error i'm seeing is caused by an incorrect test
No, the problem you stated above is not happening. The error i'm seeing is caused by an incorrect test
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-07-2014 09:18 AM
I solve the problem changing the process. Now I use a intermediate event instead of a boundary event.
I need that <java>assertTrue(signals.size() == 0);</java> pass, not fail.
Is this problem your decision or an bpm standard?
Thank you very much!
I need that <java>assertTrue(signals.size() == 0);</java> pass, not fail.
Is this problem your decision or an bpm standard?
Thank you very much!
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-08-2014 03:51 AM
The BPM standard only has global signals (so you can fire a signal from one process instance to other process instance with a different process definition even). That is what the spec defines.
We added the process-instance scoped signal ourselves, to only fire the signal event within the same process instance.
If I recall correctly, this was the reason why that assertion failed in your unit test.
We added the process-instance scoped signal ourselves, to only fire the signal event within the same process instance.
If I recall correctly, this was the reason why that assertion failed in your unit test.
