Download now Free registration required
The composition of web services involves wiring together multiple web services and having them interact often in ways not originally foreseen during their initial development. In doing so, it is unavoidable that incompatibilities may arise and need to be identified and resolved. Two services are protocol-compatible if every joint execution of these services leads to a proper final state, i.e. a state in which both services are in a final state in their respective protocols. When two services are incompatible, it may be possible to introduce an adapter to resolve their mismatches. In such cases, the service protocols are said to be adaptable. Depending on the types of mismatches, it may be possible to automatically synthesize an adapter. Automated approaches for adapter generation make the following assumptions: there is no mismatch at the interface-level, or the correct interface mappings have been provided as the input, and if there are interactions which lead to deadlocks, they are not adaptable. Approach adapter development as an iterative process consisting of both interface-level and protocol-level mismatch identification and resolution. Their approach starts from an initial set of interface matching, computed by matching the WSDL interfaces of services, and then, considering the protocol specifications of two services, identifies all the interactions that results in deadlocks. Some deadlock cases may be handled by going back to the interface matching step and refining the interface matching.
- Format: PDF
- Size: 95.7 KB