Hi Alex, Am Montag, den 16.04.2007, 08:12 -0700 schrieb Alex Boisvert: > The MEX are persisted, as well as the > messages, so you should be able to retrieve them later on using the same MEX > id. As far as I can see, they aren't persistent currently. As I described in the first message to that issue, MessageExchangeImpl.setResponse is called and sets the response to the corresponding DAO-MEX. The status is also set to RESPONSE, but in BpelRuntimeContextImpl.invocationResponse2 the retrieved DAO-MEX via BpelDAOConnection.getMessageExchange still is in state ASYNC and has no response (I verified that the same MEX-ID is used). Unfortunately I am currently very heavily loaded with work so I had no time for further investigations.
> If you have a way to reproduce this, such as a sample deployment package, > I'd be happy to debug it. I'll try to provide you a process to reproduce the behaviour, but it could take a few days. kind regards, Jan
