Intermediate timer event

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-21-2011 05:05 AM
Hello,
I implemented intermediate (catching) timer event - http://jira.codehaus.org/browse/ACT-641, I committed the code to my branch so far. I'd like to ask if there are special testcases I should add to make sure it doesn't break things (extend MultiInstanceTest?) - so far I have simple test showing it's working - https://svn.codehaus.org/activiti/activiti/branches/mproch/modules/activiti-engine/src/test/java/org...
I implemented intermediate (catching) timer event - http://jira.codehaus.org/browse/ACT-641, I committed the code to my branch so far. I'd like to ask if there are special testcases I should add to make sure it doesn't break things (extend MultiInstanceTest?) - so far I have simple test showing it's working - https://svn.codehaus.org/activiti/activiti/branches/mproch/modules/activiti-engine/src/test/java/org...
Labels:
- Labels:
-
Archive
5 REPLIES 5
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-21-2011 05:39 AM
Maciek,
Could you elaborate how you implemented it? I'm assuming you create a Job when execution arrives in the event.
When the job fires, it should just signal the wait state.
I don't see pitfalls regarding testing, since there is no interaction with the execution tree. Multi instance should also just work.
Could you elaborate how you implemented it? I'm assuming you create a Job when execution arrives in the event.
When the job fires, it should just signal the wait state.
I don't see pitfalls regarding testing, since there is no interaction with the execution tree. Multi instance should also just work.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-21-2011 05:53 AM
Cool, the BPMN coverage increases step by step 🙂

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-21-2011 06:33 AM
Joram,
yes, I create job when execution reaches this activiti - in the same way as in boundary event.
I added appropriate JobHandler, which signals waiting Activity - I added new ActivityBehaviour for that, since I didn't find any appropriate type - ReceiveTaskActivityBehaviour does basically the same, but I think it wouldn't be correct to use TaskActivity for that.
The timer definition is parsed the same way as it's done for boundary event.
So it's all pretty simple and I also don't see any pitfalls, but wanted to ask before doing any commits, since it's part of 'core' engine and I don't want to break anything
yes, I create job when execution reaches this activiti - in the same way as in boundary event.
I added appropriate JobHandler, which signals waiting Activity - I added new ActivityBehaviour for that, since I didn't find any appropriate type - ReceiveTaskActivityBehaviour does basically the same, but I think it wouldn't be correct to use TaskActivity for that.
The timer definition is parsed the same way as it's done for boundary event.
So it's all pretty simple and I also don't see any pitfalls, but wanted to ask before doing any commits, since it's part of 'core' engine and I don't want to break anything

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-21-2011 07:26 AM
Sounds OK. Feel free to commit it.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-22-2011 01:30 PM
Kudo's Maciej.
Much appreciated!
Much appreciated!
