Hi. Maybe I haven't understood 100% how ODE works. I've seen that the 3 possible outcomes of a test are "RESPONSE", "ASYNC" and "COMPLETED_OK". I've seen that in the bpel_test package most test.properties leave the "response1" line blank, meaning they expect the "COMPLETED_OK" outcome. The rest of them use a regular expression that will correspond to the "RESPONSE". The problem is that I haven't seen any test case using ASYNC. What I think happens to my process is that it takes the "ASYNC" I write in the test.properties as a regular expression, so it considers it is waiting for a RESPONSE instead of for an asyncronous answer. This makes me think that maybe there's something special in the way of using "ASYNC", and as I haven't seen any example I can't be sure of how it works (apart from the snippet in ODE's web, but it's not part of a test case).
Is there any example of how to expect an ASYNC response anywhere? I'll post my process ASAP, because I had just made a few modifications to try to continue without using the ASYNC. Thanks for answering. Sebastian Gomez. On Mon, Jun 23, 2008 at 4:25 PM, Matthieu Riou <[EMAIL PROTECTED]> wrote: > On Mon, Jun 23, 2008 at 4:34 AM, Sebastian Gomez <[EMAIL PROTECTED]> wrote: > >> Hi. >> >> I'm trying to do a test case expecting an asyncronous response. If I >> write "response1=ASYNC" in the response1 field (as it says in the ode >> user guide) I get the following error: >> >> test1.properties#1: Unexpected final message exchange status; got >> ASYNC, expected RESPONSE >> >> What am I supposed to write in the response line to expect an ASYNC >> response? >> > > Without seeing your process it's hard to tell but it's probably related to > its design. Do you have a reply for this message? If it's marked async you > shouldn't. > > Matthieu > > >> >> Thanks in advance. >> >> Sebastian Gomez. >> >
