{'fraction_non_alphanumeric': 0.02284527518172378, 'fraction_numerical': 0.0, 'mean_word_length': 4.914110429447852, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Migration Validity of WS-BPEL Instances Revisited

WS-BPEL processes ought to be adaptable even at run-time so as to adapt to the changing environments and requirements. It is cost-ineffective and time-consuming to restart a running WS-BPEL instance from scratch after the WS-BPEL process is changed. Instead, a WS-BPEL instance had better be transferred to the updated process. Current approaches to validity checking of instance migration are too conservative and thus few instance migrations are considered to be valid. To address this problem, we propose a novel criterion for valid migration which is based on the dynamic dependence graph for the trace of a WS-BPEL instance. Compared with existing approaches, our approach is significantly less conservative, that is, it allows more instances to migrate to the updated process. We illustrate the applicability and effectiveness of our approach by dynamically updating the WS-BPEL process of a travel agency.