需要澄清“运输障碍"在理解属性 [英] Need clarification on "Transport Barrier" in understanding properties
问题描述
我已阅读 Mule Floe 中的所有OUTBOUND"属性将在穿过Transport barrier"时转换为INBOUND"属性.我不明白这个运输障碍是什么意思".它是从 Mule 出站连接器调用外部世界吗?还是在 mule 项目本身内调用流程?
i have read all "OUTBOUND" properties in Mule floe will be converted to "INBOUND" properties on crossing the "Transport barrier". i could not understand what is this "Transport barrier mean" . Is it calling an external world from an Mule outbound connector ? or calling an flow within the mule project itself ?
推荐答案
传输屏障"是指您的 Mule 消息通过使用传输的端点(例如 HTTP 端点、JMS、TCP、VM等).
A "transport barrier" is when your Mule message goes through an endpoint that makes use of a transport (say for example, HTTP endpoints, JMS, TCP, VM, etc).
Mule 中有两种调用流的方式:
There are two ways of calling flows in Mule:
- 通过端点.
- 通过 Flow-Ref 组件.
第一种情况使用传输，因此，您的消息会经历整个序列化和反序列化过程.在一天结束时，您仍然会得到相同的有效载荷，但它将是不同的 Mule 消息.
The first case makes use of transports, therefore, your message goes through the whole serialization and deserialization processes. At the end of the day, you will still end up with the same payload BUT it will be a different Mule message.
在第二种情况下，流被直接调用 - Mule 消息按原样发送给被调用的流.
In the second case, flows are called directly - the Mule message is sent as is to the flow being called.
这里要强调的一件重要事情是，当流变量通过传输(因此跨越传输屏障)被调用时，它们不会传播到流.当使用 flow-ref 组件调用流时，即使 Mule 消息不在定义流变量的同一个流中，流变量仍然可以被访问.
One important thing to highlight here is that flow variables are NOT propagated to flows when they are called via a transport (therefore crossing the transport barrier). When calling flows with the flow-ref component, flow variables can STILL be accessed even though the Mule message is not in the same flow in which the flow variables were defined.
可以在此处找到有关此主题的更多信息:
More information on this topic can be found here:
http://blogs.mulesoft.org/mule-school-the-mulemessage-property-scopes-and-variables/
这篇关于需要澄清“运输障碍"在理解属性的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
