Dynamic Invocation Model of Web Services Using Subsumption Relations
ICWS '04 Proceedings of the IEEE International Conference on Web Services
Computer
Computer
Queue - Component Technologies
Semi-automated adaptation of service interactions
Proceedings of the 16th international conference on World Wide Web
Query by example for web services
Proceedings of the 2008 ACM symposium on Applied computing
An approach to adapt service requests to actual service interfaces
Proceedings of the 2008 international workshop on Software engineering for adaptive and self-managing systems
Daios: Efficient Dynamic Web Service Invocation
IEEE Internet Computing
Journal of Web Engineering
An approach to improve code-first web services discoverability at development time
Proceedings of the 27th Annual ACM Symposium on Applied Computing
Computers and Electronics in Agriculture
Towards a computer assisted approach for migrating legacy systems to SOA
ICCSA'12 Proceedings of the 12th international conference on Computational Science and Its Applications - Volume Part IV
Anti-pattern free code-first web services for state-of-the-art Java WSDL generation tools
International Journal of Web and Grid Services
Hi-index | 0.00 |
Service-Oriented Computing (SOC) allows developers to build applications by reusing and invoking Web-accessible services. SOC promotes loose coupling between applications and services, which has been mostly addressed by using techniques for Separation of Concerns (SoC). Contemporary SOC development models based on SoC either rely on difficult-to-adopt, ad-hoc programming facilities and languages or fail at isolating applications from details of the application-service interaction. We propose DI4WS, a SOC programming model that combines the well-known Adapter and Dependency Injection patterns. We show that DI4WS allows reducing couplings to services, which has a positive effect on application maintenance, without requiring developers to learn such facilities or languages. DI4WS follows a contract-last approach to service invocation, whereby developers first code the logic of their applications and then non-invasively "adapt" and "inject" required services. An empirical comparison of DI4WS with two related approaches to decouple services is also reported, showing that the DI4WS versions of 4 evaluated applications used less memory and ran faster than the others.