{'fraction_non_alphanumeric': 0.016272189349112426, 'fraction_numerical': 0.0, 'mean_word_length': 5.509615384615385, '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}}
Bridging the gap between object oriented programming and service oriented computing

Object-oriented programming languages deliver the main technology for implementing enterprise systems, but they are losing pace with the rapidly evolving paradigm of Service-Oriented Computing. This is mainly due to inadequate support for dealing with service volatility and distribution issues. In this paper, we focus on the growing distance between Java and Service Oriented Computing. First, we discuss the disadvantages of the current Java programming model in the context of developing SOA applications. Then, we provide a basis for bridging the gap between both programming paradigms.