This content has been marked as final. Show 3 replies
Thanks for the reply, but there is no issue with the one-way from bpel1 to bpel2, we do not expect nor want a response from bpel2, it should just publish the event and complete. The bpel1 should continue it's flow (which it does) and the next action is a Receive action listening for an event (that was published by bpel2), but the Receive never finds the event.
Here's a less complex use case:
1. bpelprocess1 is a synchronous process which publishes to Event1 (this completes successful and returns a success message to the client)
2. bpelprocess2 is an asynchronous process which has a mid-process Receive action that is listening for Event1
3. bpelprocess3 is a process which is initiated by Event 1
If we execute bpelprocess2 it will set at the mid-process Receive action in a PENDING state, waiting for Event1 to occur.
If we then execute bpelprocess1 the Event1 is published and we receive a "SUCCESS" response back.
At this point bpelprocess3 is initiated (b/c it's initial Receive is triggered by Event1)
We would also expect the mid-process Receive in bpelprocess2, which is in a PENDING state to trigger, but it never does.
Hopefully this use case makes more sense.