Question about activiti-rest.war and jobs

[groopk]

We are just in the beginning stages of prototyping with Activiti, and I have a couple of questions-

1) Is activiti-rest.war intended for production use?  We plan to use a standalone workflow engine and would like a rest api, so this would be a perfect fit for us.

1b)  Is there any rest client code already written that we can leverage? i.e. a domain model in java and something that maps the json responses from activiti-rest.war to the domain objects.  Not a big deal if we have to create this ourselves, but if there is already something available I would use it.

2) I have a question about "jobs" (the kind mentioned here: http://www.activiti.org/userguide/index.html#exclusiveJobs).  If I understand correctly, when a Java Service node is encountered while executing a workflow, activiti puts an entry in the database for that job to be completed. Then activiti goes into a wait state. Then a job executor picks up the job and executes it in a new thread. When the job is finished, activiti picks up the results and continues.  Is that accurate?

Thanks

[frederikherema1]

1) Although the REST-api currently does not cover the full Java Actvivti API, it's production-ready. Please note that in 5.13, there will be an overhaul of the REST to support more (or the full) API and make it more consistent.

1b) Currently, I'm not aware of such a client-framework I'm afraid.

2) Almost correct. Only the last part is slightly different. The job-executor-thread that executes the job will execute the async service-task AND the rest of the process until a wait-state has been reached, another async-activity or the end of the process.