[
https://issues.apache.org/jira/browse/ODE-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101229#comment-13101229
]
Tammo van Lessen edited comment on ODE-939 at 9/9/11 2:16 PM:
--------------------------------------------------------------
I thought this is what
org.apache.ode.bpel.engine.BpelRuntimeContextImpl.failOutstandingMessageExchanges()
is good for. Perhaps it is just not working as expected...
was (Author: vanto):
I thought this is what
org.apache.ode.bpel.engine.BpelRuntimeContextImpl.failOutstandingMessageExchanges()
is good for. Perhaps it is just malfunctioning...
> Fault missingReply is not thrown
> --------------------------------
>
> Key: ODE-939
> URL: https://issues.apache.org/jira/browse/ODE-939
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3.5
> Reporter: Gary Brown
> Attachments: hwnoreply.zip
>
>
> According to the BPEL spec, the 'missingReply' fault should be: "Thrown when
> an inbound message activity has been executed, and the process instance or
> scope instance reaches the end of its execution without a corresponding
> <reply> activity having been executed."
> The attached is a simple hello world example with a missing reply. The
> process instance reaches the end, but does not throw the fault, and instead
> the client (e.g. soapui) simply times out.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
