02-17-2012 12:58 PM
02-21-2012 04:19 PM
If you're running the process in the Activiti demo setup, you should make sure your classes are on Tomcat's classpath when starting Activiti - that is, the classes are not and should not be part of the .bar file. If you look in your deployment folder in the project, you can see there's also a .jar file that's created. If you have the class in the same project, it should be in that jar, so it's all ready-made for you. Otherwise, you will need to create a jar containing the class yourself. Then you can drop the jar in Tomcat's lib directory for a quick solution. Most approaches for a more "enterprisey" solution tend to suggest repackaging activiti-rest and including the jar using Maven. You can then run that war on any container, because it contains Activiti, the REST API and your process' classes.
02-21-2012 04:28 PM
10-11-2012 07:20 AM
<definitions xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:activiti="http://activiti.org/bpmn" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:smileysurprised:mgdc="http://www.omg.org/spec/DD/20100524/DC" xmlns:smileysurprised:mgdi="http://www.omg.org/spec/DD/20100524/DI" typeLanguage="http://www.w3.org/2001/XMLSchema" expressionLanguage="http://www.w3.org/1999/XPath" targetNamespace="http://www.activiti.org/test">
<process id="document_processing" name="Document Processing">
<startEvent id="startevent1" name="Start"></startEvent>
<serviceTask id="task_indexing" name="Indexing (Service Task)" activiti:class="com.unisys.activiti.prototype.IndexService" activiti:resultVariableName="input"></serviceTask>
<endEvent id="endevent1" name="End"></endEvent>
10-11-2012 08:43 AM
10-01-2013 10:04 AM
10-02-2013 06:01 AM
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.