your scenario is completely valid and I can confirm that it works - we tested it on Riftsaw 2.3.1 Final. In my experience you need to reconfigure the default failure handling on the invoke activity for the failover to work. Please see bellow. Also please note that failover may take longer because of the preset mex.timeout.
Invoke from our test:
<bpel:invoke name="invokeOk" partnerLink="external" operation="reportResultAndAttemptJvmKill" portType="ns1:NotificationWS" inputVariable="okRequest" outputVariable="invokeOutput">
For more info on activity failure/recovery please see: http://ode.apache.org/activity-failure-and-recovery.html
Hope this helps.
Thanks for confirming and providing this additional info Marek. I'll do some more testing and give an update.
Yeah, please use the acvitity recover feature that Marek suggested for this case. INVOKE and WAIT activity has been implemented differently here.