If a change is made to any aspect of a service that is coupled, then either the requester or the provider application code (or, more likely, both) will have to change.
如果耦合的服务任何方面有所变化，那么，请求者或提供者的应用程序代码(更可能是两者同时)必须改变。
The service requester and the mediation flow component itself did not change at all, hence no programming was involved.
服务请求者和中介流组件本身根本不会发生改变，因此不涉及到编程工作。
The ultimate solution is described at the Semantic level - dynamic service definitions where "the definition of the service interface must change based on the context of the service requester."
最后的解决方案是在语义级别描述的——动态服务定义，其中“服务接口的定义必须基于服务请求者的上下文改变。”
The actual provider is known only to the ESB, and in fact, may change without impact to the requester.
实际提供者仅对ESB 可知，并且事实上可以更改而不影响请求者。
If the requester already exists, then it already has a specific binding to an implementation that you must change to point to the mediation module's export.
如果请求者已经存在，则该请求者已经具有一个特定的到某个实现的绑定，您必须更改该实现以指向中介模块的导出。
This is a bit of a change for the requester because under normal WS-RM processing rules, once a message is acknowledged, it would not need to be resent.
这需要对请求方进行一点修改，因为在普通 WS-RM处理逻辑中，消息得到确认后，就不再需要对其进行重发了。
This is a bit of a change for the requester because under normal WS-RM processing rules, once a message is acknowledged, it would not need to be resent.
这需要对请求方进行一点修改，因为在普通 WS-RM处理逻辑中，消息得到确认后，就不再需要对其进行重发了。
应用推荐