topic Re: Listening to Lifecycle events (start, end, transitions) in Alfresco Archive

Listening to Lifecycle events (start, end, transitions)

jjfutt — Thu, 22 Mar 2012 02:42:13 GMT

update: 3/22/2012After going through the CDI section of documentation and the examples in ActivitiInAction book, I now understand that part of my question was just wrong and was a consequence of my bad understanding of differences between CDI (JSR299) vs Spring. I am going to ask my new question in

Re: Listening to Lifecycle events (start, end, transitions)

p4w3l — Sat, 09 Jun 2012 11:20:40 GMT

Just have exciting weekend with CDI so can share experience, strenght and hope:

No need for EJB. No need to configure anything ( except activiti-cdi ). Say you tested activiti-cdi working for you. As a minimal test I would say that the below works for you instead of:

   processEngine = ProcessEngines.getDefaultProcessEngine();
   identityService = processEngine.getIdentityService();

you use:
private @Inject IdentityService identityService;
Then you update activiti-context.xml with what you referenced and create a POJO with method you referenced say with e content like:
log.debug( businessProcessEvent );then you see in log every stupid event of every running process

Re: Listening to Lifecycle events (start, end, transitions)

jjfutt — Fri, 15 Jun 2012 01:50:39 GMT

Thanks a lot for the help – I will be checking this out this weekend. Thanks again.

Re: Listening to Lifecycle events (start, end, transitions)

smcardle — Sat, 03 Aug 2013 03:52:09 GMT

What happened to these classes in the 5.13 release ????

There is no longer a class BpmnParseListener and no setCustomPostBPMNParseListeners(…) method on the ProcessEngineConfigurationImpl.

So in 5.13 how do I now setup the engine so that I can hook into all of the process engine events ?

Steve

Re: Listening to Lifecycle events (start, end, transitions)

frederikherema1 — Mon, 05 Aug 2013 08:42:32 GMT

They are refactored to have a cleaner model. It's now called BPMNParseHandlers…