Thanks Martin. I have managed to trigger the diagram's MessageIntermediateCatchEvent with the above line of code running in an external JAR. Thanks for the help Martin
The only issue that remains is how to trigger an external JAR from ServiceTask1 to run code outside of Activiti. I am trying to use the below code, but it doesnt actually trigger the jar, and hence the diagram just waits at the IntermediateMessageCatchEvent. Is there something wrong with my command? This code works fine when triggered from a command line, as it then triggers the messagecatchevent which is waiting in activiti.
<code>
public void execute(DelegateExecution execution) {
String s;
Process p;
try {
p = Runtime.getRuntime().exec("java -cp StandaloneRunner.jar
tandaloneRunner_lib/* conceptclasses.StandaloneRunner " + execution.getId());
System.out.println("Execution command triggered");
BufferedReader br = new BufferedReader(
new InputStreamReader(p.getInputStream()));
while ((s = br.readLine()) != null)
System.out.println("line: " + s);
p.waitFor();
System.out.println ("exit: " + p.exitValue());
p.destroy();
} catch (Exception e) {
e.printStackTrace();
}
}
The only issue that remains is how to trigger an external JAR from ServiceTask1 to run code outside of Activiti. I am trying to use the below code, but it doesnt actually trigger the jar, and hence the diagram just waits at the IntermediateMessageCatchEvent. Is there something wrong with my command? This code works fine when triggered from a command line, as it then triggers the messagecatchevent which is waiting in activiti.
<code>
public void execute(DelegateExecution execution) {
String s;
Process p;
try {
p = Runtime.getRuntime().exec("java -cp StandaloneRunner.jar
tandaloneRunner_lib/* conceptclasses.StandaloneRunner " + execution.getId());System.out.println("Execution command triggered");
BufferedReader br = new BufferedReader(
new InputStreamReader(p.getInputStream()));
while ((s = br.readLine()) != null)
System.out.println("line: " + s);
p.waitFor();
System.out.println ("exit: " + p.exitValue());
p.destroy();
} catch (Exception e) {
e.printStackTrace();
}
}
Thanks Vasile, placing it in the bin folder allows the JAR to run
One point to note is that the process instance id that is passed to the jar isnt the id that triggers the messagecatchevent. I needed to add a separate step to interrogate the database for child messagecatchevent1 id's in order to trigger the element itself to continue.
I also second the notion that this sort of functionality should be part of Activiti, as there will always be a case where we want a Service Task to last a while before it moves on, just like any real business task, they can take time. I suggest the database timeout is either increased, or its scope to be public so it can be changed easily in the Explorer or through Java.
One point to note is that the process instance id that is passed to the jar isnt the id that triggers the messagecatchevent. I needed to add a separate step to interrogate the database for child messagecatchevent1 id's in order to trigger the element itself to continue.
I also second the notion that this sort of functionality should be part of Activiti, as there will always be a case where we want a Service Task to last a while before it moves on, just like any real business task, they can take time. I suggest the database timeout is either increased, or its scope to be public so it can be changed easily in the Explorer or through Java.
