Service task is not working in case of timer start event ?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2012 07:09 AM
Scenario is :
timer start event - service task - end node
when the above flow is deployed to activiti exploer , it is not able to instantiate the java class referred by the service task .
but at the same time
start event - service task - end node
works fine . In the second flow , the same java class is referred .
Why service task is not able to refer to the java class in activiti explorer when fired through timer start event ?
timer start event - service task - end node
when the above flow is deployed to activiti exploer , it is not able to instantiate the java class referred by the service task .
but at the same time
start event - service task - end node
works fine . In the second flow , the same java class is referred .
Why service task is not able to refer to the java class in activiti explorer when fired through timer start event ?
Labels:
- Labels:
-
Archive
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2012 07:42 AM
The only way I see a difference is in the fact that the start-event runs in the job-executer instead of the http-request-thread. This should be no problem, unless your job-executor is in another VM, web app.
Do you have the activiti-rest web app running as del on the same engine in that tomcat? In that case, it should have the jar with the class on it's class path as well…
Do you have the activiti-rest web app running as del on the same engine in that tomcat? In that case, it should have the jar with the class on it's class path as well…
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2012 08:40 AM
thnx frederik , the app jars were not in activiti-rest lib .
