Registering an implementation of TaskLifeCycleEventListener
Tony Cattlin
Tony Cattlin
Maciej Swiderski
--
You received this message because you are subscribed to the Google Groups "jBPM Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-development+unsubscribe@googlegroups.com.
To post to this group, send email to jbpm-development@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-development/85787334-bc60-4c8c-9cb7-fd05016130a2%40googlegroups.com.
Tony Cattlin
Maciej Swiderski
Tony Cattlin
You received this message because you are subscribed to a topic in the Google Groups "jBPM Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jbpm-development/nTyEmIkUl8o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jbpm-development+unsubscribe@googlegroups.com.
To post to this group, send email to jbpm-development@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-development/2F5BE880-4B14-46B5-8004-2373D5026991%40gmail.com.
Maciej Swiderski
Tony Cattlin
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<deployment-descriptor xsi:schemaLocation="http://www.jboss.org/jbpm deployment-descriptor.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<persistence-unit>org.jbpm.domain</persistence-unit>
<audit-persistence-unit>org.jbpm.domain</audit-persistence-unit>
<audit-mode>JPA</audit-mode>
<persistence-mode>JPA</persistence-mode>
<runtime-strategy>SINGLETON</runtime-strategy>
<marshalling-strategies/>
<event-listeners>
<event-listener>
<resolver>mvel</resolver>
<identifier>new com.db.nms.incr.IncrEventListener(ksession)</identifier>
<parameters/>
</event-listener>
</event-listeners>
<task-event-listeners>
<task-event-listener>
<resolver>mvel</resolver>
<identifier>new com.db.nms.incr.IncrTaskListener(runtimeManager)</identifier>
</task-event-listener>
</task-event-listeners>
<globals/>
<work-item-handlers>
<work-item-handler>
<resolver>mvel</resolver>
<identifier>new com.db.nms.incr.IncrProcessSupportHandler()</identifier>
<parameters/>
<name>IncrProcessSupport</name>
</work-item-handler>
</work-item-handlers>
<environment-entries/>
<configurations/>
<required-roles/>
<remoteable-classes/>
</deployment-descriptor>
Maciej Swiderski
Tony Cattlin
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<deployment-descriptor xsi:schemaLocation="http://www.jboss.org/jbpm deployment-descriptor.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<persistence-unit>org.jbpm.domain</persistence-unit>
<audit-persistence-unit>org.jbpm.domain</audit-persistence-unit>
<audit-mode>JPA</audit-mode>
<persistence-mode>JPA</persistence-mode>
<runtime-strategy>SINGLETON</runtime-strategy>
<marshalling-strategies/>
<event-listeners>
<event-listener>
<resolver>mvel</resolver>
<identifier>new com.db.nms.incr.IncrEventListener()</identifier>
<parameters/>
</event-listener>
</event-listeners>
<task-event-listeners>
<!-- task-event-listener>
<resolver>mvel</resolver>
<identifier>new com.db.nms.incr.IncrTaskListener(runtimeManager)</identifier>
</task-event-listener-->
</task-event-listeners>
<globals/>
<work-item-handlers>
<!-- work-item-handler>
<resolver>mvel</resolver>
<identifier>new com.db.nms.incr.IncrProcessSupportHandler()</identifier>
<parameters/>
<name>IncrProcessSupport</name>
</work-item-handler-->
</work-item-handlers>
<environment-entries/>
<configurations/>
<required-roles/>
<remoteable-classes/>
</deployment-descriptor>
package com.db.nms.incr;
import java.sql.Timestamp;
import java.util.Arrays;
import java.util.Date;
import java.util.HashMap;
import org.apache.log4j.Logger;
import org.jbpm.ruleflow.instance.RuleFlowProcessInstance;
import org.jbpm.workflow.core.impl.ExtendedNodeImpl;
import org.jbpm.workflow.instance.node.HumanTaskNodeInstance;
import org.kie.api.event.process.ProcessCompletedEvent;
import org.kie.api.event.process.ProcessEventListener;
import org.kie.api.event.process.ProcessNodeLeftEvent;
import org.kie.api.event.process.ProcessNodeTriggeredEvent;
import org.kie.api.event.process.ProcessStartedEvent;
import org.kie.api.event.process.ProcessVariableChangedEvent;
import org.kie.api.runtime.process.NodeInstance;
import org.kie.api.runtime.process.WorkflowProcessInstance;
public class IncrEventListener implements ProcessEventListener {
public void beforeProcessStarted(ProcessStartedEvent event) {
//logger.info("beforeProcessStarted:" + event.getProcessInstance().getProcessName());
}
public void afterProcessStarted(ProcessStartedEvent event) {
logger.info("afterProcessStarted:" + event.getProcessInstance().getProcessName());
}
public void beforeProcessCompleted(ProcessCompletedEvent event) {
//logger.info("beforeProcessCompleted:" + event.getProcessInstance().getProcessName());
}
public void afterProcessCompleted(ProcessCompletedEvent event) {
logger.info("afterProcessCompleted:" + event.getProcessInstance().getProcessName());
}
public void beforeNodeTriggered(ProcessNodeTriggeredEvent event) {
}
public void afterNodeTriggered(ProcessNodeTriggeredEvent event) {
}
public void beforeNodeLeft(ProcessNodeLeftEvent event) {
}
public void afterNodeLeft(ProcessNodeLeftEvent event) {
logHumanTaskNodeInstance("afterNodeLeft", event.getNodeInstance());
}
public void beforeVariableChanged(ProcessVariableChangedEvent event) {
//logger.info("beforeVariableChanged:" + event.getVariableId());
}
public void afterVariableChanged(ProcessVariableChangedEvent event) {
//logger.info("afterVariableChanged:" + event.getVariableId());
}
private void logHumanTaskNodeInstance(String event, NodeInstance nodeInstance) {
}
}
Tony Cattlin
private static final Logger logger = Logger.getLogger(IncrEventListener.class);
Maciej Swiderski
Tony Cattlin
// ksession.addEventListener(new IncrEventListener());
And if I put the line below in my kmodule.xml it also works fine. The reason for switching to the deployment descriptor is to get the taskEventhandler working.
<processEventListener type="com.db.nms.incr.IncrEventListener"/>
So I assume as these work fine that log4j is on the classpath in both scenarios.
Tony Cattlin
Tony Cattlin
<kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
<kbase name="kbaseincr" packages="com.db.nms.incr">
<ksession name="ksessionincr">
<listeners>
<processEventListener type="com.db.nms.incr.IncrEventListener"/>
<taskEventListener type="com.db.nms.incr.IncrTaskListener"/>
</listeners>
</ksession>
</kbase>
</kmodule>