You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Jan Loewe <ja...@pilgerer.org> on 2007/04/12 21:52:52 UTC
Invalid response state for mex: ASYNC
Hi all,
I am currently trying to call a simple external web-service using
<invoke> and getting a reply. My service gets called and the reply is
send. I digged into the source a bit and
MessageExchangeImpl.setResponse(Message outputMessage) is called and as
far as I understand this means, that the message is fine. But then,
later in BpelRuntimeContextImpl.invocationResponse2(String mexid,
InvokeResponseChannel responseChannel), I get a MEX that has no response
attached to it. Am I right, that there should be one, as long as the
MEX-ID is the same? The MEX I get has also its status set to ASYNC, so
the error mentioned in the topic appears. I will attach my BPEL and WSDL
files, maybe I'm just too stupid to understand BPEL.
regards,
Jan