Conversation Errors in Web Service Coordination Run-time Detection and Repair.pdf

Conversation Errors in Web Service Coordination Run-time Detection and Repair.pdf

  1. 1、本文档共8页,可阅读全部内容。
  2. 2、有哪些信誉好的足球投注网站(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
  3. 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  4. 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
Conversation Errors in Web Service Coordination Run-time Detection and Repair

Conversation Errors in Web Service Coordination: Run-time Detection and Repair Warren Blanchet, Renée Elio, and Eleni Stroulia Department of Computing Science University of Alberta {blanchet, ree, stroulia}@cs.ualberta.ca Abstract Organizations that own web services participating in a workflow composition may evolve their components independently. Service coordination can fail when previously legal messages between independently changing, distributed components become illegal because their respective workflow models are no longer synchronized. This paper presents an intelligent-agent framework that wraps a web service in a conversation layer and a simple workflow-adaptation function. The conversation layer implements protocols and consults globally shared, declarative policy specifications to resolve interaction failures. The framework allows agents to resolves various model mismatches that cause interaction errors, including changes to required preconditions, partners, and expected message ordering. Implications of this distributed approach to web service coordination are also discussed. 1. Introduction One of the appealing elements of web service composition is its distributed conceptualization: functional components of a system are implemented as network-accessible “services” declaratively specified (in WSDL) and declaratively composed (in BPEL4WS). However, most of the available middleware environments that support this composition assume that the coordination specification, which defines conversation controllers, is interpreted by a central middleware node. This poses some interesting issues for bottom-up Enterprise Application Integration, in which the various organizations that own the services participating in the workflow may evolve their services independently. The question then becomes “how should a composition evolve with its independently changing, constituent services?”. For example, suppose that Organization A adds new preconditions that must be satis

文档评论(0)

l215322 + 关注
实名认证
内容提供者

该用户很懒,什么也没介绍

1亿VIP精品文档

相关文档