Getting task details
The final
query-based operation we need to implement is getOrderDetails, which returns the order details for the specified orderNo. The Task Query Service provides two similar operations: getTaskDetailsByNumber and
getTaskDetailsById.
As the orderNo corresponds to the taskNumber, it makes sense to call the getTaskDetailsByNumber operation. This just takes the standard workflowContext and the taskNumber as its input.
The only slight area of complexity is extracting the order from the task payload. This is because payload is defined as xsd:any, which means it can contain any value. Because of this, the XPath mapping tool can't determine the structure of the payload and thus can't visually map the From part of the operation. ...
Get Oracle SOA Suite 11g R1 Developer's Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
