Hello Oders,
I think i just found a bug in the ODE trunk in ExtensionContext. The
scenario is
- An extension Activity extending AbstractAsynchExtensionOperation
- the run method does neither complete with errors nor it completes
successfully (intended!)
- a java timer waits 10 seconds and the calls context.completeWithFault.
- then the activity gets marked as faulted, but the process runs until it is
stopped by the 30 second axis2 call timeout.
I think the situation that the activity gets marked as faulted is somehow
not propagated to the navigator, as the process could be completed just
after the timer fires (e.g. after 10 seconds, as shown above).
Does this seem plausible? If someone is interested i can supply the
extension code and the according bpel file.
greets
Chris
