OSB callback response problem

Question

Hi.
I have OSB service to route asynchronous (request-callback) service.
When I test OSB service I see that inbound message is transformed well and service is invoked.
Also I see fault
<con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-382510</con:errorCode>
     <con:reason>
     OSB Assign action failed updating variable "transformedResponse": com.bea.wli.common.xquery.XQueryException: Error parsing XML: {err}FORG0005: expected exactly one item, got 0 items
     </con:reason>
     <con:location>
     <con:node>DefaultRouteNode</con:node>
     <con:path>response-pipeline</con:path>
     </con:location>
</con:fault>
I can't understand what response can cause this fault because invoked service still running and callback is not inoked.
Why I get immediate response from asynchronous service?
What cause start of Response Action pipe?
Thanks for response.

Answer 1

I changed response pipe ... add Assign $body to $body1 and Report it at the start of response pipe, add Assign $body to $body2 and Report it at the end of response pipe.
Route to [ TerminalService ] invoking [ process ]
Request Actions:
Assign [ XQuery Resource... ]
XQuery Resource: Project/Processes/TerminalService/TerminalServiceRequest Variable Names And Bindings: source - $body/ter:process
to [ transformedRequest ]
Replace [ node contents ] of [ . ]
in [ body ] with [ $transformedReq... ]
$transformedRequest
Response Actions:
Assign [ $body ]
$body
to [ body1 ]
Report [ $body1 ]
$body1
Assign [ XQuery Resource... ]
XQuery Resource: Project/Processes/TerminalService/TerminalServiceResponse Variable Names And Bindings: sourceProcessResponse - $body/ter:processResponse
to [ transformedResponse ]
Replace [ node contents ] of [ . ]
in [ body ] with [ $transformedRes... ]
$transformedResponse
Assign [ $body ]
$body
to [ body2 ]
Report [ $body2 ]
$body2
In invocation trace is only $body1 with value (reported value is the same)
<soapenv:Body      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <ter:process>
     <ter:serviceId>1</ter:serviceId>
     </ter:process>
</soapenv:Body>
It looks like request message not response. (Routing properties "Use inbound operation for outbound" is unchecked.)
Edited by: Peter551059 on Jun 13, 2011 3:48 PM