Unable to assign multiple nodes

Question

Hi
I am trying human task over here. My case-study scenario is like this:
I am a clerk. I've the job of passing on the files to my supervisor. I've number of files with number of details which I am maintaining as array of valueobjects. Now I'll pass onto these array of VO's to my supervisor. So that he can click on one of the ids and get the specific details to the item clicked. I am introducing a human task after invoking my process from where I am getting an array of VO's. Now I need to assign these array to Human Task. I tried to assign but it gives me the following error in the BPEL Console.
<selectionFailure xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/">
<part name="summary">
<summary>XPath query string returns multiple nodes.
According to BPEL4WS spec 1.1 section 14.3, The assign activity part and query /ns1:retrieveSupervisorWorkOrderStatus1Response/return should not return multipe nodes.
Please check the BPEL source at line number "150" and verify the part and xpath query /ns1:retrieveSupervisorWorkOrderStatus1Response/return.
</summary>
</part>
</selectionFailure>
The id which supervisor clicks to get the details, I want that Id to be my response from the Human task.
Can anyone tell me as to how to go for it? How to assign the multiple nodes in the Human Task and How to get back the response?
Thanks & Regards

Answer 1

Hmm weird.
Only thing i could think of is that the transformation is getting executed before the assign.
After the transformation the field task:taskDefinitionURI isnt there anymore...in the initiateTask i mean.
Still dont think your transformation is correct. You only map a few fields, so after this, the initiateTask will only contain something like :
<task:task>
<task:systemMessageAttributes>
<task:textAttribute1>
<xsl:value-of select="workorderId"/>
</task:textAttribute1>
</task:systemMessageAttributes>
<task:systemMessageAttributes>
<task:textAttribute1>
<xsl:value-of select="workorderId"/>
</task:textAttribute1>
</task:systemMessageAttributes>
<task:systemMessageAttributes>
<task:textAttribute1>
<xsl:value-of select="workorderId"/>
</task:textAttribute1>
</task:systemMessageAttributes>
</task:task>
This isn't a valid definition of the task-variable.
    <element name="task">
      <complexType>
        <sequence>
          <element name="title" type="xsd:string" minOccurs="0"/>
          <element name="payload" type="xsd:anyType" minOccurs="1" maxOccurs="1"/>
          <element name="taskDefinitionURI" type="xsd:string" minOccurs="0"/>
          <element name="creator" type="xsd:string" minOccurs="0"/>
          <element name="ownerUser" type="xsd:string" minOccurs="0"/>
          <element name="ownerGroup" type="xsd:string" minOccurs="0"/>
          <element name="priority" type="tns:priorityType" minOccurs="0"/>
          <element name="identityContext" type="xsd:string" minOccurs="0"/>
          <element name="userComment" type="tns:commentType" minOccurs="0" maxOccurs="unbounded"/>
          <element name="attachment" type="tns:attachmentType" minOccurs="0" maxOccurs="unbounded"/>
          <element name="processInfo" type="tns:processType" minOccurs="0"/>
          <element name="systemAttributes" type="tns:systemAttributesType" minOccurs="0"/>
          <element name="systemMessageAttributes" type="tns:systemMessageAttributesType" minOccurs="0"/>
          <element name="titleResourceKey" type="xsd:string" minOccurs="0"/>
          <element name="callback" type="tns:callbackType" minOccurs="0"/>
          <element name="identificationKey" type="xsd:string" minOccurs="0"/>
        </sequence>
      </complexType>
    </element>so only 1 element of systemMessageAttributes allowed.
the same for the content in the systemMessageAttributes element.
<element name="textAttribute1" type="xsd:string" minOccurs="0"/>only one element of textAttribute1 allowed.
so guess you still need to fix your transformation.