...
The following excerpt shows how this channel binding is configured using XML:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<composite name="ProducerComposite" ...> <component name="TestProducer"> <implementation.java class="..."/> <producer name="channel" target="TestChannel"/> </component> </composite> <composite name="ChannelComposite"...> <channel name="TestChannel"> <f3:binding.zeromq/> </channel> </composite> <composite name="ConsumerComposite" ...> <component name="TestConsumer"> <implementation.java class="..."/> <consumer name="channel" source="TestChannel"/> </component> </composite> |
Consuming External Event Streams
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<composite ...>
<channel name="TestChannel">
<f3:binding.zeromq addresses="192.0.2.1:12001 192.0.2.2:12001""/>
</channel>
<component name="TestConsumer">
<implementation.java class="..."/>
<consumer name="channel" source="TestChannel"/>
</component>
</composite>
|
Publishing to External Event Streams
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<composite ...> <component name="TestProducer"> <implementation.java class="..."/> <producer name="channel" target="TestChannel"/> </component> <channel name="TestChannel"> <f3:binding.zeromq addresses="192.0.2.1:12001"/> </channel> </composite> |
...
In addition, it is highly recommended to use the bytecode proxy generation extension (Maven coordinates: org.codehaus.fabric3:fabric3-bytecode-proxy) to avoid the overhead and object creation associated with JDK proxies.
...