In the WS-BPEL example, the customer WS-BPEL generated
process is not valid, because it implies that a
response can be received in an exception handler that
is disassociated from the invoke related to the request.
Normally, if a request is separated from its associated
response, the BPEL validation rules would complain due
to the synchronous nature of the invoke activity. This
specific situation probably dues not get picked up, as
the response is not within the scope of the activities
checked by that validation rule.
Therefore it is likely that a new validation rule is
required to detect such disassociated responses.
The only other alternative would be if there was some
way to detect that the receipt of the response was in
the exception handler, and therefore receive the
response in the normal way (i.e. via the invoke), but
then cause the exception handler to be triggered - not
sure this is practical.
The problem is that this will put constraints on the
design of the service side, as it is being constrained
by the nature of the synchronous invoke on the client -
but this is necessary to maintain a consistent global
model.