Are you sure you have associated a task with the conversation?
The process is a long running one and cant be in the conversation scope.
I am just starting with seam but as I understood you can inject something from a business scope into a conversation scope.
From the docs:
Resumes work on an incomplete jBPM task. Specifies that a long-running conversation begins when this method returns a non-null outcome without exception. This conversation is associated with the jBPM task specified in the named request parameter. Within the context of this conversation, a business process context is also defined, for the business process instance of the task instance.
The jBPM TaskInstance will be available in a request context variable named taskInstance. The jPBM ProcessInstance will be available in a request context variable named processInstance
taskIdParameter ? the name of a request parameter which holds the id of the task. Default to "taskId", which is also the default used by the Seam taskList JSF component.
After doing the above
I would have thought that
would do exactly the same as the code you have?
Is that not the case?
I would be interested to know how you get on.
Seems like you have to use jbpm (original post) calls in the action handlers as the seam interceptors do not fire and hence cant us @In in the ActionHandler