简体   繁体   English

什么是SOA中的“包装服务”?

[英]What is a “wrapper service” in SOA?

I have looked on the web but I am confused as to whether a wrapper service wraps a legacy application, or a set of complex services. 我已经在网上查看了但是我对包装器服务是否包装遗留应用程序或一组复杂服务感到困惑。

Update: Judging by the answers I have received there is no accepted definition for a "wrapper service" in SOA, and after further investigation I realised that "wrapper services" depends on who defines it. 更新:根据我收到的答案判断,SOA中的“包装器服务”没有可接受的定义,经过进一步调查后,我意识到“包装器服务”取决于谁定义它。 I mean in an Oracle context. 我的意思是在Oracle上下文中。

All - part of the confusion around this term stems from simply being mis-spoken... 所有 - 围绕这个术语的一部分混乱源于简单地被误解......

It's NOT "wrapper SERVICE", but rather "service WRAPPER" :-) 它不是“包装服务”,而是“服务WRAPPER”:-)

Once you get the TERM itself correct, things start to make sense: - a "wrapper SERVICE" sounds like a SERVICE which creates "wrappers" - WRONG; 一旦你使TERM本身正确,事情开始变得有意义: - “包装服务”听起来像一个创建“包装”的服务 - 错误; - a "service WRAPPER" sounds like code which encapsulates or "wraps" an existing body of code, and gives it the ability to act as a SERVICE - RIGHT ! - “服务WRAPPER”听起来像是封装或“包装”现有代码体的代码,并赋予其作为服务的能力 - 正确!

It's now obvious we're talking about SERVICE WRAPPERS here, and now it starts to become clear(er) that it DOESN'T EVEN MATTER what sort of code is encapsulated "inside" the wrapper, because the wrapper code acts like a FUNCTION, where there is a "interface" (established input formats & output formats) that is all the users interact with, making the guts inside a "black box" the user NEVER needs to know about... 现在显而易见的是,我们在这里讨论的是SERVICE WRAPPERS,现在它开始变得清晰(呃),它在包装器“内部”封装了什么类型的代码并不重要,因为包装器代码就像一个FUNCTION,所有用户都与之交互的“界面”(已建立的输入格式和输出格式),使用户无需了解的“黑匣子”内胆......

This wrapper then presents to the user as something like a FUNCTION; 然后,这个包装器向用户呈现类似于FUNCTION的东西; the user submits inputs to the "service"... and gets back outputs. 用户将输入提交给“服务”...并获取输出。 The wrapper itself then has code which internally interacts with the legacy or new code inside the wrapper, formulates an output, and returns this output to the requester (user) :-) ... 然后包装器本身具有代码,该代码在内部与包装器内的旧代码或新代码交互,形成输出,并将此输出返回给请求者(用户):-) ...

Historically service wrappers were the favorite way to re-purpose legacy code which did NOT all by itself behave like services (background-running programs capable of listening & responding to requests, aka daemon processes), but as organizations worked to evolved toward SOA, this was a great way to quickly turn legacy "apps" - typically NOT running in background - into services. 从历史上看,服务包装器是重新使用遗留代码的最佳方式,这些代码本身并不像服务一样(能够监听和响应请求的后台运行程序,也称守护进程),但随着组织努力向SOA发展,是一种很好的方式可以快速将传统的“应用程序”(通常不在后台运行)转换为服务。

Hope this helps. 希望这可以帮助。 -MV markvogt.vogtland.ws -MV markvogt.vogtland.ws

我将包装器服务理解为包装某些东西的服务,无论是另一种服务,一组服务还是遗留应用程序。

"wrapper service" which is also more widely known as "legacy wrapper" is used to wrap a legacy component to prevent coupling issues in soa. “包装器服务”也被广泛称为“遗留包装器”,用于包装遗留组件以防止soa中的耦合问题。

hiding complex systems or a set of services is done using the "facade service" 隐藏复杂系统或一组服务是使用“门面服务”完成的

Arguably the entire point about SOA is that everything is a wrapper. 关于SOA的全部观点可以说是一切都是包装器。 That is , a web service is just a facade, and there is no way to tell whether it fronts a "legacy application" or "a set of complex services". 也就是说,Web服务只是一个外观,没有办法判断它是“传统应用程序”还是“一组复杂服务”。

包装器服务是一个或多个Web服务的组合,其封装了不同模块的逻辑,由此单个模块能够以最小的集成问题与其他模块通信。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM