[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: clarity of example in Section 10.2
Hi, editor-team, When I am applying changes for Issue 37 to Section 10.2., I am re-reading the example in that section. If my reading is correct, we don't have invoice-CS related information in PurchaseOrderResponse, we may want to improve the clarity of the example by adding the following to the BPEL sample code. ---------------------- <xsd:complexType name="PurchaseOrderResponse"> <xsd:element name="CID" type="xsd:string"/> <xsd:element name="order" type="xsd:int"/> <xsd:element name="VID" type="xsd:string"/> <!-- *adding* --> <xsd:element name="invNum" type="xsd:int"/> <!-- *adding* --> ... </xsd:complexType> ---------------------- --------------- <bpws:propertyAlias propertyName="cor:vendorID" messageType="tns:InvMessage" part="IVC"> <query> /IVC/VID </query> </bpws:propertyAlias> <bpws:propertyAlias propertyName="cor:invoiceNumber" messageType="tns:InvMessage" part="IVC"> <query> /IVC/InvNum </query> </bpws:propertyAlias> <!-- *adding* --> <bpws:propertyAlias propertyName="cor:vendorID" messageType="tns:PurchaseOrderResponse" part="IVC"> <query> ... </query> </bpws:propertyAlias> <!-- *adding* --> <bpws:propertyAlias propertyName="cor:invoiceNumber" messageType="tns:PurchaseOrderResponse" part="IVC"> <query> ... </query> </bpws:propertyAlias> --------------- (BTW, we of course need to rectify the XPath used in the query subelement after passing Issue 103) It should either look like this: <bpws:propertyAlias propertyName="cor:vendorID" messageType="tns:InvMessage" part="IVC"> <query>/VID</query> </bpws:propertyAlias> or look like this: <bpws:propertyAlias propertyName="cor:vendorID" messageType="tns:InvMessage"> <query>/IVC/VID</query> </bpws:propertyAlias> What do you guys think? Regards, Alex Yiu |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]