gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Resolves checkstyle errors for eip-* (#1069)

Browse Source 
* Reduces checkstyle errors in eip-aggregator

* Reduces checkstyle errors in eip-message-channel

* Reduces checkstyle errors in eip-publish-subscribe

* Reduces checkstyle errors in eip-splitter

* Reduces checkstyle errors in eip-wire-tap
This commit is contained in:
Anurag Agarwal
2019-11-10 23:04:42 +05:30
committed by Ilkka Seppälä
parent f2c91eb836
commit 7c888e8886
9 changed files with 68 additions and 69 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
eip-message-channel/src/main/java/com/iluwatar/eip/message/channel/App.java
View File

@ -30,12 +30,11 @@ import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
/**
*
* 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 Channel decouples Message
* producers and consumers.
* <p>
* The sending application doesn't necessarily know what particular application will end up
*
* <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
@ -44,19 +43,18 @@ import org.slf4j.LoggerFactory;
* 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 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.
*
*
* <p>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 {
private static final Logger LOGGER = LoggerFactory.getLogger(App.class);
/**
* Program entry point
* Program entry point.
*/
public static void main(String[] args) throws Exception {
CamelContext context = new DefaultCamelContext();