#173 Removed unneeded dependencies

This commit is contained in:
adkm 2017-10-17 00:12:41 +02:00
parent 9c7ee5ed1d
commit 767f41ad90
3 changed files with 11 additions and 5 deletions

View File

@ -40,11 +40,6 @@
<artifactId>camel-core</artifactId>
<version>${camel.version}</version>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-csv</artifactId>
<version>${camel.version}</version>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>

View File

@ -7,9 +7,17 @@ import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.context.ConfigurableApplicationContext;
/**
* It is very common in integration systems that incoming messages consists of many items bundled together. For example
* an invoice document contains multiple invoice lines describing transaction (quantity, name of provided
* service/sold goods, price etc.). Such bundled messages may not be accepted by other systems. This is where splitter
* pattern comes in handy. It will take the whole document, split it based on given criteria and send individual
* items to the endpoint.
*
* <p>
* Splitter allows you to split messages based on defined criteria. It takes original message, process it and send
* multiple parts to the output channel. It is not defined if it should keep the order of items though.
* </p>
*
*/
@SpringBootApplication
public class App {

View File

@ -7,6 +7,9 @@ import org.springframework.stereotype.Component;
* Sample splitter route definition.
*
* <p>
* It consumes messages out of the <i>direct:entry</i> entry point and forwards them to <i>direct:endpoint</i>.
* Route accepts messages having body of array or collection of objects. Splitter component split message body and
* forwards single objects to the endpoint.
* </p>
*
* In this example input/output endpoints names are stored in <i>application.properties</i> file.