Apparently, I quite misunderstood the way the email receiver QPAC interacts with Workflow server. :-) Sorry for having bothered you with silly questions. Now, I got the workflow working!
Still I get the 'cannot coerce object' exception. The example workflow stalls executing the task 'Str -> Form'.
> com.adobe.workflow.datatype.InvalidCoercionException: Cannot coerce object: com.adobe.workflow.dom.VariableAttr@7935a1 of type:
>
com.adobe.workflow.dom.VariableAttr to type: com.adobe.workflow.datatype.form.FormDataTypeInstance
>
at com.adobe.workflow.datatype.form.FormDataHandler.coerceFrom(FormDataHandler.java:220)
>
at com.adobe.workflow.datatype.AbstractComplexDataTypeHandler.getNode(AbstractComplexDataTypeHandler.java:42)
>
at com.adobe.workflow.dom.VariableElement.setBoundValue(VariableElement.java:72)
>
at com.adobe.workflow.pat.service.PATExecutionContextImpl.setProcessDataValue(PATExecutionContextImpl.java:398)
>
at com.adobe.workflow.pat.service.PATExecutionContextImpl.setProcessDataWithExpression(PATExecutionContextImpl.java:310)
>
at com.adobe.workflow.qpac.set_value.SetValueService.execute(SetValueService.java:72)
>
at com.adobe.workflow.engine.PEUtil.executeAction(PEUtil.java:184)
>
at com.adobe.workflow.engine.ProcessEngineBMTBean.continueBranchAtAction(ProcessEngineBMTBean.java:2320)
>
at com.adobe.workflow.engine.ProcessEngineBMTBean.asyncContinueBranchCommand(ProcessEngineBMTBean.java:1903)
>
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
[...]
Howard, in the forum thread
Question about Email Receiver QPAC you told Rob to provide a patch. Does this patch solves the 'cannot coerce object' problem?