From f74c8c27d1afdcacfac71318f9efd8337a129bca Mon Sep 17 00:00:00 2001 From: Ilkka Seppala Date: Wed, 2 Sep 2015 21:42:32 +0300 Subject: [PATCH] #143 Added second message channel. --- .../src/main/java/com/iluwatar/message/channel/App.java | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/message-channel/src/main/java/com/iluwatar/message/channel/App.java b/message-channel/src/main/java/com/iluwatar/message/channel/App.java index bf86fe3f9..f9a334a8a 100644 --- a/message-channel/src/main/java/com/iluwatar/message/channel/App.java +++ b/message-channel/src/main/java/com/iluwatar/message/channel/App.java @@ -21,9 +21,10 @@ import org.apache.camel.impl.DefaultCamelContext; * doesn't pull info off some random channel; it selects what channel to get information * from based on what type of information it wants. *

- * In this example we use Apache Camel to establish a direct synchronous Message Channel - * that delivers messages to console output. No actual messages are sent, only the established - * routes are printed to standard output. + * In this example we use Apache Camel to establish two different Message Channels. The first + * one reads from standard input and delivers messages to Direct endpoint. The second Message + * Channel is established from the Direct component to console output. No actual messages are sent, + * only the established routes are printed to standard output. * */ public class App { @@ -40,6 +41,7 @@ public class App { @Override public void configure() throws Exception { + from("stream:in").to("direct:greetings"); from("direct:greetings").to("stream:out"); } });