topic Transaction driven events in Alfresco Archive

Transaction driven events

mishamo — Thu, 14 Aug 2014 11:09:19 GMT

Hi,A colleague of mine reported https://jira.codehaus.org/browse/ACT-2040 a while ago. I have recently attempted to address the issue myself and thought I'd report on my findings and see if I can get some feedback on the approach.As a quick summary, the issue was that although an ActivitiEvent may c

Re: Transaction driven events

mishamo — Thu, 14 Aug 2014 11:56:40 GMT

I also realised that no events seem to be fired after a call to <code>taskService.unclaim(taskId)</code>. Is that by design or an oversight? I suppose I would expect at least a TASK_ASSIGNED event to be fired.

Re: Transaction driven events

jbarrez — Tue, 19 Aug 2014 09:50:31 GMT

In Activiti 5.16, there is an easier way now: see https://github.com/Activiti/Activiti/blob/master/modules/activiti-engine/src/main/java/org/activiti/engine/impl/event/logger/EventLogger.java , the onEvent method. You can add stuff to the current command context and also get a close notification.

> I also realised that no events seem to be fired after a call to taskService.unclaim(taskId)

That does sound like a bug to me.

Re: Transaction driven events

mishamo — Tue, 19 Aug 2014 15:44:40 GMT

I'm assuming you're referring to the <code>CommandContextCloseListener</code>. In that case, is there any difference between the command context being closed and the transaction context being closed?

Regarding the bug, shall I raise it in JIRA?

Re: Transaction driven events

jbarrez — Tue, 19 Aug 2014 20:45:58 GMT

> In that case, is there any difference between the command context being closed and the transaction context being closed?

Yes, the command context close happens after transaction commit, but just before the transaction context is closed

> Regarding the bug, shall I raise it in JIRA?

Not needed, already fixed it today in https://github.com/Activiti/Activiti/commit/a30b42bd423dc3ce4754bafa18adbcc6decd00fd 🙂