Hi Jan, I didn't go through everything in detail but I spotted what might be an issue with your process. The last <reply> references a different operation "helloOut" than the first <receive> operation "hello". This might be the cause of the ASYNC status since the <reply> isn't matched to the <receive>. I guess the compiler should at least complain that "helloOut" isn't a valid operatoin for the HelloWorld portType.
alex On 4/12/07, Jan Loewe <[EMAIL PROTECTED]> wrote:
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
