iluwatar#143 Commented the example

iluwatar · iluwatar · commit 96dc4cdddb3a · 2015-08-22T19:33:11.000+03:00
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
@@ -4,8 +4,35 @@
 import org.apache.camel.builder.RouteBuilder;
 import org.apache.camel.impl.DefaultCamelContext;
 
+/**
+ * 
+ * When two applications communicate with each other using a messaging system
+ * they first need to establish a communication channel that will carry the
+ * data. Message Channels are logical addresses in the messaging system.
+ * <p>
+ * The sending application doesn't necessarily know what particular application
+ * will end up retrieving it, but it can be assured that the application that
+ * retrieves the information is interested in that information. This is because
+ * the messaging system has different Message Channels for different types of
+ * information the applications want to communicate. When an application sends
+ * information, it doesn't randomly add the information to any channel available;
+ * it adds it to a channel whose specific purpose is to communicate that sort of
+ * information. Likewise, an application that wants to receive particular information
+ * doesn't pull info off some random channel; it selects what channel to get information
+ * from based on what type of information it wants.
+ * <p>
+ * 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.
+ * 
+ */
 public class App {
-	
+
+	/**
+	 * Program entry point
+	 * @param args command line args
+	 * @throws Exception
+	 */
 	public static void main(String[] args) throws Exception {
 		CamelContext context = new DefaultCamelContext();
 		
