Version models for software configuration management
ACM Computing Surveys (CSUR)
Large Scale, Type-Compatible Service Composition
ICWS '04 Proceedings of the IEEE International Conference on Web Services
Interoperability among independently evolving web services
Proceedings of the 5th ACM/IFIP/USENIX international conference on Middleware
A design technique for evolving web services
CASCON '06 Proceedings of the 2006 conference of the Center for Advanced Studies on Collaborative research
Odyssey-SCM: An integrated software configuration management infrastructure for UML models
Science of Computer Programming
Preserving XML queries during schema evolution
Proceedings of the 16th international conference on World Wide Web
Supporting the dynamic evolution of Web service protocols in service-oriented architectures
ACM Transactions on the Web (TWEB)
The Challenges of Service Evolution
CAiSE '08 Proceedings of the 20th international conference on Advanced Information Systems Engineering
Managing the Evolution of Service Specifications
CAiSE '08 Proceedings of the 20th international conference on Advanced Information Systems Engineering
Using an Interface Proxy to Host Versioned Web Services
SCC '08 Proceedings of the 2008 IEEE International Conference on Services Computing - Volume 2
On Synchronizing with Web Service Evolution
ICWS '08 Proceedings of the 2008 IEEE International Conference on Web Services
Automatically Determining Compatibility of Evolving Services
ICWS '08 Proceedings of the 2008 IEEE International Conference on Web Services
When are two web services compatible?
TES'04 Proceedings of the 5th international conference on Technologies for E-Services
International Journal of Web Services Research
Test Pair Selection for Test Case Prioritization in Regression Testing for WS-BPEL Programs
International Journal of Web Services Research
Hi-index | 0.00 |
A major advantage of Service-Oriented Architectures SOA is composition and coordination of loosely coupled services. Because the development lifecycles of services and clients are de-coupled, multiple service versions must be maintained to support older clients. Typically versions are managed within the SOA by updating service descriptions using conventions on version numbers and namespaces. In all cases, the compatibility among services descriptions must be evaluated, which can be hard, error-prone and costly if performed manually, particularly for complex descriptions. In this paper, the authors describe a method to automatically determine when two service descriptions are backward compatible. The authors describe a case study to illustrate version compatibility information in a SOA environment and present initial performance overheads. By automatically exploring compatibility information, a service developers can assess the impact of proposed changes; b proper versioning requirements can be put in client implementations guaranteeing that incompatibilities will not occur during run-time; and c messages exchanged in the SOA can be validated to ensure that only expected messages or compatible ones are exchanged.