Language Support for Service Interactions in Service-Oriented Architecture
- Cite this paper as:
- De Labey S., Boydens J., Steegmans E. (2010) Language Support for Service Interactions in Service-Oriented Architecture. In: Maciaszek L.A., González-Pérez C., Jablonski S. (eds) Evaluation of Novel Approaches to Software Engineering. ENASE 2008. Communications in Computer and Information Science, vol 69. Springer, Berlin, Heidelberg
The Open Services Gateway initiative (OSGi) is a platform for running service-oriented Java applications. OSGi provides a central service registry to allow application components (so-called bundles) to share functionality. From the viewpoint of programming language development, OSGi leaves a lot of room for improvement. Its service query language, for instance, bypasses important compile-time guarantees and it works only for service metadata that never changes during the lifetime of a service. A second problem is that the event notification system requires programmers to write a considerable amount of boilerplate logic for reacting to service events. This obfuscates the business logic, which in turn decreases code comprehension and increases the odds for introducings bugs when implementing client-service interactions.
This paper evaluates OSGi as a platform for programming client-service interactions in Java. After focusing on problems that relate to OSGi’s integrated service query language and its event notification system, we propose a solution based on a programming language extension. We also show how this extension is transformed to regular Java code so as to maintain interoperability with the OSGi specification.
KeywordsService-Oriented Architecture Language Concepts
Unable to display preview. Download preview PDF.