http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/file-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/file-component.adoc b/camel-core/src/main/docs/file-component.adoc index fea8057..66934da 100644 --- a/camel-core/src/main/docs/file-component.adoc +++ b/camel-core/src/main/docs/file-component.adoc @@ -6,7 +6,7 @@ The File component provides access to file systems, allowing files to be processed by any other Camel link:components.html[Components] or messages from other components to be saved to disk. -### URI format +=== URI format [source,java] ---------------------------- @@ -47,9 +47,9 @@ your environment. To help with this Camel provides different `readLock` options and `doneFileName` option that you can use. See also the section _Consuming files from folders where others drop files directly_. -### URI Options +=== URI Options -#### File2 Options +#=== File2 Options // component options: START @@ -166,12 +166,12 @@ with the following path and query parameters: -#### Default behavior for file producer +#=== Default behavior for file producer * By default it will override any existing file, if one exist with the same name. -### Move and Delete operations +=== Move and Delete operations Any move or delete operations is executed after (post command) the routing has completed; so during processing of the `Exchange` the file @@ -235,7 +235,7 @@ You can combine the *pre* move and the regular move: So in this situation, the file is in the `inprogress` folder when being processed and after it's processed, it's moved to the `.done` folder. -#### Fine grained control over Move and PreMove option +#=== Fine grained control over Move and PreMove option The *move* and *preMove* options are link:expression.html[Expression]-based, so we have the full power of @@ -257,7 +257,7 @@ the pattern, we can do: move=backup/${date:now:yyyyMMdd}/${file:name} --------------------------------------------- -#### About moveFailed +#=== About moveFailed The `moveFailed` option allows you to move files that *could not* be processed succesfully to another location such as a error folder of your @@ -267,11 +267,11 @@ timestamp you can use See more examples at link:file-language.html[File Language] -### Message Headers +=== Message Headers The following headers are supported by this component: -#### File producer only +#=== File producer only [width="100%",cols="10%,90%",options="header",] |======================================================================= @@ -295,7 +295,7 @@ if the option `fileName` has been configured, then this is still being evaluated. |======================================================================= -#### File consumer only +#=== File consumer only [width="100%",cols="10%,90%",options="header",] |======================================================================= @@ -328,11 +328,11 @@ relative filename. For absolute files this is the absolute path. *Camel 2.10.3 and older* the type is `Date`. |======================================================================= -### Batch Consumer +=== Batch Consumer This component implements the link:batch-consumer.html[Batch Consumer]. -#### Exchange Properties, file consumer only +#=== Exchange Properties, file consumer only As the file consumer implements the `BatchConsumer` it supports batching the files it polls. By batching we mean that Camel will add the @@ -356,7 +356,7 @@ This allows you for instance to know how many files exist in this batch and for instance let the link:aggregator2.html[Aggregator2] aggregate this number of files. -### Using charset +=== Using charset *Available as of Camel 2.9.3* + The charset option allows for configuring an encoding of the files on @@ -444,7 +444,7 @@ DEBUG GenericFileConverter - Read file /Users/davsclaus/workspace/came DEBUG FileOperations - Using Reader to write file: target/charset/output.txt with charset: iso-8859-1 ---------------------------------------------------------------------------------------------------------------------------------------------- -### Common gotchas with folder and filenames +=== Common gotchas with folder and filenames When Camel is producing files (writing files) there are a few gotchas affecting how to set a filename of your choice. By default, Camel will @@ -484,14 +484,14 @@ And a syntax where we set the filename on the endpoint with the from("direct:report").to("file:target/reports/?fileName=report.txt"); --------------------------------------------------------------------- -### Filename Expression +=== Filename Expression Filename can be set either using the *expression* option or as a string-based link:file-language.html[File Language] expression in the `CamelFileName` header. See the link:file-language.html[File Language] for syntax and samples. -### Consuming files from folders where others drop files directly +=== Consuming files from folders where others drop files directly Beware if you consume files from a folder where other applications write files to directly. Take a look at the different readLock options to see @@ -506,7 +506,7 @@ good at detecting this. You may also want to look at the doneFileName option, which uses a marker file (done file) to signal when a file is done and ready to be consumed. -### Using done files +=== Using done files *Available as of Camel 2.6* @@ -554,7 +554,7 @@ from("file:bar?doneFileName=ready-${file:name}"); * `hello.txt` - is the file to be consumed * `ready-hello.txt` - is the associated done file -### Writing done files +=== Writing done files *Available as of Camel 2.6* @@ -601,16 +601,16 @@ was `foo.txt` in the same directory as the target file. Will for example create a file named `foo.done` if the target file was `foo.txt` in the same directory as the target file. -### Samples +=== Samples -#### Read from a directory and write to another directory +#=== Read from a directory and write to another directory [source,java] ----------------------------------------------------------- from("file://inputdir/?delete=true").to("file://outputdir") ----------------------------------------------------------- -#### Read from a directory and write to another directory using a overrule dynamic name +#=== Read from a directory and write to another directory using a overrule dynamic name [source,java] --------------------------------------------------------------------------------------------- @@ -621,7 +621,7 @@ Listen on a directory and create a message for each file dropped there. Copy the contents to the `outputdir` and delete the file in the `inputdir`. -#### Reading recursively from a directory and writing to another +#=== Reading recursively from a directory and writing to another [source,java] -------------------------------------------------------------------------- @@ -669,7 +669,7 @@ outputdir/foo.txt outputdir/bar.txt ----------------- -#### Reading from a directory and the default move operation +#=== Reading from a directory and the default move operation Camel will by default move any processed file into a `.camel` subdirectory in the directory the file was consumed from. @@ -698,7 +698,7 @@ outputdir/foo.txt outputdir/sub/bar.txt --------------------------- -#### Read from a directory and process the message in java +#=== Read from a directory and process the message in java [source,java] ----------------------------------------------------------- @@ -713,13 +713,13 @@ from("file://inputdir/").process(new Processor() { The body will be a `File` object that points to the file that was just dropped into the `inputdir` directory. -#### Writing to files +#=== Writing to files Camel is of course also able to write files, i.e. produce files. In the sample below we receive some reports on the SEDA queue that we process before they are being written to a directory. -#### Write to subdirectory using `Exchange.FILE_NAME` +#=== Write to subdirectory using `Exchange.FILE_NAME` Using a single route, it is possible to write a file to any number of subdirectories. If you have a route setup as such: @@ -744,7 +744,7 @@ Exchange.FILE_NAME = foo/bye.txt => /rootDirectory/foo/bye.txt This allows you to have a single route to write files to multiple destinations. -#### Writing file through the temporary directory relative to the final destination +#=== Writing file through the temporary directory relative to the final destination Sometime you need to temporarily write the files to some directory relative to the destination directory. Such situation usually happens @@ -760,7 +760,7 @@ from("direct:start"). to("file:///var/myapp/finalDirectory?tempPrefix=/../filesInProgress/"); ------------------------------------------------------------------------- -#### Using expression for filenames +#=== Using expression for filenames In this sample we want to move consumed files to a backup folder using today's date as a sub-folder name: @@ -772,7 +772,7 @@ from("file://inbox?move=backup/${date:now:yyyyMMdd}/${file:name}").to("..."); See link:file-language.html[File Language] for more samples. -### Avoiding reading the same file more than once (idempotent consumer) +=== Avoiding reading the same file more than once (idempotent consumer) Camel supports link:idempotent-consumer.html[Idempotent Consumer] directly within the component so it will skip already processed files. @@ -822,7 +822,7 @@ consumed before: DEBUG FileConsumer is idempotent and the file has been consumed before. Will skip this file: target\idempotent\report.txt ------------------------------------------------------------------------------------------------------------------------- -#### Using a file based idempotent repository +#=== Using a file based idempotent repository In this section we will use the file based idempotent repository `org.apache.camel.processor.idempotent.FileIdempotentRepository` instead @@ -842,7 +842,7 @@ idempotent repository and define our file consumer to use our repository with the `idempotentRepository` using `#` sign to indicate link:registry.html[Registry] lookup: -#### Using a JPA based idempotent repository +#=== Using a JPA based idempotent repository In this section we will use the JPA based idempotent repository instead of the in-memory based that is used as default. @@ -893,7 +893,7 @@ option: </route> --------------------------------------------------------------------------------- -### Filter using org.apache.camel.component.file.GenericFileFilter +=== Filter using org.apache.camel.component.file.GenericFileFilter Camel supports pluggable filtering strategies. You can then configure the endpoint with such a filter to skip certain files being processed. @@ -916,7 +916,7 @@ spring XML file: </route> ---------------------------------------------------------- -#### Filtering using ANT path matcher +#=== Filtering using ANT path matcher TIP:*New options from Camel 2.10 onwards* There are now `antInclude` and `antExclude` options to make it easy to @@ -937,7 +937,7 @@ The file paths is matched with the following rules: The sample below demonstrates how to use it: -### Sorting using Comparator +=== Sorting using Comparator Camel supports pluggable sorting strategies. This strategy it to use the build in `java.util.Comparator` in Java. You can then configure the @@ -968,7 +968,7 @@ link:registry.html[Registry] by prefixing the id with `#`. So writing `sorter=#mySorter`, will instruct Camel to go look in the link:registry.html[Registry] for a bean with the ID, `mySorter`. -### Sorting using sortBy +=== Sorting using sortBy Camel supports pluggable sorting strategies. This strategy it to use the link:file-language.html[File Language] to configure the sorting. The @@ -1056,7 +1056,7 @@ per group, so we could reverse the file names: sortBy=date:file:yyyyMMdd;reverse:file:name ------------------------------------------- -### Using GenericFileProcessStrategy +=== Using GenericFileProcessStrategy The option `processStrategy` can be used to use a custom `GenericFileProcessStrategy` that allows you to implement your own @@ -1077,7 +1077,7 @@ resources etc. * in the `commit()` method we can move the actual file and also delete the _ready_ file. -### Using filter +=== Using filter The `filter` option allows you to implement a custom filter in Java code by implementing the `org.apache.camel.component.file.GenericFileFilter` @@ -1090,7 +1090,7 @@ directories, to avoid traversing down unwanted directories. For example to skip any directories which starts with `"skip"` in the name, can be implemented as follows: -### How to use the Camel error handler to deal with exceptions triggered outside the routing engine +=== How to use the Camel error handler to deal with exceptions triggered outside the routing engine The file and ftp consumers, will by default try to pickup files. Only if that is successful then a Camel link:exchange.html[Exchange] can be @@ -1142,7 +1142,7 @@ class="com.foo.MyExceptionHandler"/>: The source code for this example can be seen https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/component/file/FileConsumerCustomExceptionHandlerTest.java[here] -#### Using consumer.bridgeErrorHandler +#=== Using consumer.bridgeErrorHandler *Available as of Camel 2.10* @@ -1164,12 +1164,12 @@ does *not* apply. The link:exchange.html[Exchange] is processed directly by the Camel link:error-handler.html[Error Handler], and does not allow prior actions such as interceptors, onCompletion to take action. -### Debug logging +=== Debug logging This component has log level *TRACE* that can be helpful if you have problems. -### See Also +=== See Also * link:configuring-camel.html[Configuring Camel] * link:component.html[Component]
http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/file-language.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/file-language.adoc b/camel-core/src/main/docs/file-language.adoc index 39d9a3d..9bc0591 100644 --- a/camel-core/src/main/docs/file-language.adoc +++ b/camel-core/src/main/docs/file-language.adoc @@ -14,7 +14,7 @@ path and names. The goal is to allow expressions to be used with the link:file2.html[File] and link:ftp.html[FTP] components for setting dynamic file patterns for both consumer and producer. -### File Language options +=== File Language options // language options: START The File language supports 2 options which are listed below. @@ -29,7 +29,7 @@ The File language supports 2 options which are listed below. |=== // language options: END -### Syntax +=== Syntax This language is an *extension* to the link:simple.html[Simple] language so the link:simple.html[Simple] syntax applies also. So the table below @@ -100,9 +100,9 @@ the file. Notice: all the commands from the link:simple.html[Simple] language can also be used. |======================================================================= -### File token example +=== File token example -#### Relative paths +#=== Relative paths We have a `java.io.File` handle for the file `hello.txt` in the following *relative* directory: `.\filelanguage\test`. And we configure @@ -134,7 +134,7 @@ tokens will return as: |file:absolute.path |\workspace\camel\camel-core\target\filelanguage\test\hello.txt |======================================================================= -#### Absolute paths +#=== Absolute paths We have a `java.io.File` handle for the file `hello.txt` in the following *absolute* directory: @@ -168,7 +168,7 @@ return as: |file:absolute.path |\workspace\camel\camel-core\target\filelanguage\test\hello.txt |======================================================================= -### Samples +=== Samples You can enter a fixed link:constant.html[Constant] expression such as `myfile.txt`: @@ -226,7 +226,7 @@ use the link:file-language.html[File Language], link:simple.html[Simple] and the link:bean.html[Bean] language in one combined expression. This is pretty powerful for those common file path patterns. -### Using Spring PropertyPlaceholderConfigurer together with the link:file2.html[File] component +=== Using Spring PropertyPlaceholderConfigurer together with the link:file2.html[File] component In Camel you can use the link:file-language.html[File Language] directly from the link:simple.html[Simple] language which makes a @@ -290,6 +290,6 @@ Invalid bean definition with name 'sampleRoute' defined in class path resource [ Could not resolve placeholder 'date:now:yyyyMMdd' ---------------------------------------------------------------------------------------------------- -### Dependencies +=== Dependencies The File language is part of *camel-core*. http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/gzip-dataformat.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/gzip-dataformat.adoc b/camel-core/src/main/docs/gzip-dataformat.adoc index 7f4876e..6eb255c 100644 --- a/camel-core/src/main/docs/gzip-dataformat.adoc +++ b/camel-core/src/main/docs/gzip-dataformat.adoc @@ -12,7 +12,7 @@ The compression capability is quite useful when you deal with large XML and Text based payloads or when you read messages previously comressed using `gzip` tool. -### Options +=== Options // dataformat options: START The GZip dataformat supports 1 options which are listed below. @@ -26,7 +26,7 @@ The GZip dataformat supports 1 options which are listed below. |=== // dataformat options: END -### Marshal +=== Marshal In this example we marshal a regular text/XML payload to a compressed payload employing gzip compression format and send it an ActiveMQ queue @@ -37,7 +37,7 @@ called MY_QUEUE. from("direct:start").marshal().gzip().to("activemq:queue:MY_QUEUE"); -------------------------------------------------------------------- -### Unmarshal +=== Unmarshal In this example we unmarshal a gzipped payload from an ActiveMQ queue called MY_QUEUE to its original format, and forward it for processing to @@ -48,7 +48,7 @@ the `UnGZippedMessageProcessor`. from("activemq:queue:MY_QUEUE").unmarshal().gzip().process(new UnGZippedMessageProcessor()); --------------------------------------------------------------------------------------------- -### Dependencies +=== Dependencies This data format is provided in *camel-core* so no additional dependencies is needed. http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/header-language.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/header-language.adoc b/camel-core/src/main/docs/header-language.adoc index 144268b..728f2f9 100644 --- a/camel-core/src/main/docs/header-language.adoc +++ b/camel-core/src/main/docs/header-language.adoc @@ -5,7 +5,7 @@ The Header Expression Language allows you to extract values of named headers. -### Header Options +=== Header Options // language options: START The Header language supports 1 options which are listed below. @@ -19,7 +19,7 @@ The Header language supports 1 options which are listed below. |=== // language options: END -### Example usage +=== Example usage The recipientList element of the Spring DSL can utilize a header expression like: @@ -38,6 +38,6 @@ notice that header is not a parameter but a stacked method call) from("direct:a").recipientList().header("myHeader"); ------------------------------------------------------ -### Dependencies +=== Dependencies The Header language is part of *camel-core*. http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/language-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/language-component.adoc b/camel-core/src/main/docs/language-component.adoc index 54bf66b..6150fe3 100644 --- a/camel-core/src/main/docs/language-component.adoc +++ b/camel-core/src/main/docs/language-component.adoc @@ -16,7 +16,7 @@ additional JARs is needed. You only have to include additional Camel components if the language of choice mandates it, such as using link:groovy.html[Groovy] or link:javascript.html[JavaScript] languages. -### URI format +=== URI format [source,java] ------------------------------------------ @@ -32,7 +32,7 @@ link:language.html[Language]s in Camel language://languageName:resource:scheme:location][?options] ----------------------------------------------------------- -### URI Options +=== URI Options // component options: START @@ -74,7 +74,7 @@ with the following path and query parameters: // endpoint options: END -### Message Headers +=== Message Headers The following message headers can be used to affect the behavior of the component @@ -87,7 +87,7 @@ component script configured on the endpoint. |======================================================================= -### Examples +=== Examples For example you can use the link:simple.html[Simple] language to link:message-translator.html[Message Translator] a message: @@ -108,7 +108,7 @@ Object out = producer.requestBodyAndHeader("language:xpath", "<foo>Hello World</ assertEquals("Hello World", out); -------------------------------------------------------------------------------------------------------------------------------- -### Loading scripts from resources +=== Loading scripts from resources *Available as of Camel 2.9* @@ -129,7 +129,7 @@ From *Camel 2.11* onwards you can refer to the resource similar to the other link:language.html[Language]s in Camel by prefixing with `"resource:"` as shown below: -### See Also +=== See Also * link:configuring-camel.html[Configuring Camel] * link:component.html[Component] http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/log-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/log-component.adoc b/camel-core/src/main/docs/log-component.adoc index 32e8a2d..7edeb90 100644 --- a/camel-core/src/main/docs/log-component.adoc +++ b/camel-core/src/main/docs/log-component.adoc @@ -14,7 +14,7 @@ logging via, among others: http://java.sun.com/j2se/1.4.2/docs/api/java/util/logging/package-summary.html[JDK Util Logging logging] -### URI format +=== URI format [source,java] ----------------------------- @@ -51,7 +51,7 @@ There is also a `log` directly in the DSL, but it has a different purpose. Its meant for lightweight and human logs. See more details at link:logeip.html[LogEIP]. -### Options +=== Options @@ -123,7 +123,7 @@ with the following path and query parameters: // endpoint options: END -### Regular logger sample +=== Regular logger sample In the route below we log the incoming orders at `DEBUG` level before the order is processed: @@ -144,7 +144,7 @@ Or using Spring XML to define the route: </route> --------------------------------------------------- -### Regular logger with formatter sample +=== Regular logger with formatter sample In the route below we log the incoming orders at `INFO` level before the order is processed. @@ -155,7 +155,7 @@ from("activemq:orders"). to("log:com.mycompany.order?showAll=true&multiline=true").to("bean:processOrder"); -------------------------------------------------------------------------------------- -### Throughput logger with groupSize sample +=== Throughput logger with groupSize sample In the route below we log the throughput of the incoming orders at `DEBUG` level grouped by 10 messages. @@ -166,7 +166,7 @@ from("activemq:orders"). to("log:com.mycompany.order?level=DEBUG&groupSize=10").to("bean:processOrder"); ----------------------------------------------------------------------------------- -### Throughput logger with groupInterval sample +=== Throughput logger with groupInterval sample This route will result in message stats logged every 10s, with an initial 60s delay and stats should be displayed even if there isn't any @@ -185,7 +185,7 @@ The following will be logged: "Received: 1000 new messages, with total 2000 so far. Last group took: 10000 millis which is: 100 messages per second. average: 100" ------------------------------------------------------------------------------------------------------------------------------------ -### Masking sensitive information like password +=== Masking sensitive information like password *Available as of Camel 2.19* You can enable security masking for logging by setting `logMask` flag to `true`. @@ -227,7 +227,7 @@ If you want to use a custom masking formatter, put it into registry with the nam Note that the masking formatter must implement `org.apache.camel.spi.MaskingFormatter`. -### Full customization of the logging output +=== Full customization of the logging output *Available as of Camel 2.11* @@ -309,7 +309,7 @@ options: <to uri="log:bar?param1=bar&param2=200"/> --------------------------------------------- -#### Using Log component in OSGi +#=== Using Log component in OSGi *Improvement as of Camel 2.12.4/2.13.1* @@ -325,7 +325,7 @@ should be the bundle which contains route definition. To do this, either register single instance of `org.slf4j.Logger` in the Registry or reference it using `logger` URI parameter. -### See Also +=== See Also * link:configuring-camel.html[Configuring Camel] * link:component.html[Component] http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/mock-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/mock-component.adoc b/camel-core/src/main/docs/mock-component.adoc index 6469b94..56d80a7 100644 --- a/camel-core/src/main/docs/mock-component.adoc +++ b/camel-core/src/main/docs/mock-component.adoc @@ -9,7 +9,7 @@ ifdef::env-github[] :warning-caption: :warning: endif::[] -### Mock Component +=== Mock Component link:testing.html[Testing] of distributed and asynchronous processing is notoriously difficult. The link:mock.html[Mock], link:test.html[Test] @@ -65,7 +65,7 @@ From Camel 2.10 onwards there are two new options `retainFirst`, and endpoints keep in memory. -### URI format +=== URI format [source] ---- @@ -78,7 +78,7 @@ endpoint. You can append query options to the URI in the following format, `?option=value&option=value&...` -### Options +=== Options @@ -129,7 +129,7 @@ with the following path and query parameters: -### Simple Example +=== Simple Example Here's a simple example of Mock endpoint in use. First, the endpoint is resolved on the context. Then we set an expectation, and then, after the @@ -156,7 +156,7 @@ Camel will by default wait 10 seconds when the `assertIsSatisfied()` is invoked. This can be configured by setting the `setResultWaitTime(millis)` method. -#### Using `assertPeriod` +#=== Using `assertPeriod` *Available as of Camel 2.7* + When the assertion is satisfied then Camel will stop waiting and @@ -179,7 +179,7 @@ resultEndpoint.expectedMessageCount(2); resultEndpoint.assertIsSatisfied(); ---- -### Setting expectations +=== Setting expectations You can see from the Javadoc of http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/mock/MockEndpoint.html[MockEndpoint] @@ -223,7 +223,7 @@ Here's another example: resultEndpoint.expectedBodiesReceived("firstMessageBody", "secondMessageBody", "thirdMessageBody"); ---- -#### Adding expectations to specific messages +#=== Adding expectations to specific messages In addition, you can use the http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/mock/MockEndpoint.html#message(int)[`message(int @@ -243,7 +243,7 @@ There are some examples of the Mock endpoint in use in the http://svn.apache.org/viewvc/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/[`camel-core` processor tests]. -### Mocking existing endpoints +=== Mocking existing endpoints *Available as of Camel 2.7* @@ -312,7 +312,7 @@ That means Camel will use more memory. This may not be suitable when you send in a lot of messages. -#### Mocking existing endpoints using the `camel-test` component +#=== Mocking existing endpoints using the `camel-test` component Instead of using the `adviceWith` to instruct Camel to mock endpoints, you can easily enable this behavior when using the `camel-test` Test @@ -332,7 +332,7 @@ include::../../../../components/camel-test/src/test/java/org/apache/camel/test/p ---- -#### Mocking existing endpoints with XML DSL +#=== Mocking existing endpoints with XML DSL If you do not use the `camel-test` component for unit testing (as shown above) you can use a different approach when using XML files for @@ -372,7 +372,7 @@ in the constructor for the bean: </bean> ---- -#### Mocking endpoints and skip sending to original endpoint +#=== Mocking endpoints and skip sending to original endpoint *Available as of Camel 2.10* @@ -398,7 +398,7 @@ The same example using the link:testing.html[Test Kit] include::../../../../components/camel-test/src/test/java/org/apache/camel/test/patterns/IsMockEndpointsAndSkipJUnit4Test.java[tags=e1] ---- -### Limiting the number of messages to keep +=== Limiting the number of messages to keep *Available as of Camel 2.10* @@ -435,7 +435,7 @@ methods that work on message bodies, headers, etc. will only operate on the retained messages. In the example above they can test only the expectations on the 10 retained messages. -### Testing with arrival times +=== Testing with arrival times *Available as of Camel 2.7* @@ -491,7 +491,7 @@ In the example above we use `seconds` as the time unit, but Camel offers `milliseconds`, and `minutes` as well. -### See Also +=== See Also * link:configuring-camel.html[Configuring Camel] * link:component.html[Component] http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/properties-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/properties-component.adoc b/camel-core/src/main/docs/properties-component.adoc index 02c7bcf..b332634 100644 --- a/camel-core/src/main/docs/properties-component.adoc +++ b/camel-core/src/main/docs/properties-component.adoc @@ -2,7 +2,7 @@ *Available as of Camel version 2.3* -### URI format +=== URI format [source] ---- @@ -11,7 +11,7 @@ properties:key[?options] Where *key* is the key for the property to lookup -### Options +=== Options // component options: START The Properties component supports 17 options which are listed below. @@ -79,7 +79,7 @@ with the following path and query parameters: You can use the method `resolvePropertyPlaceholders` on the `CamelContext` to resolve a property from any Java code. -### Using PropertyPlaceholder +=== Using PropertyPlaceholder *Available as of Camel 2.3* @@ -114,7 +114,7 @@ service idiom. * *Camel 2.14.1* Using custom functions, which can be plugged into the property component. -### Syntax +=== Syntax The syntax to use Camel's property placeholder is to use `{{key}}` for example `{{file.uri}}` where `file.uri` is the property key. @@ -130,7 +130,7 @@ NOTE: Do not use colon in the property key. The colon is used as a separator token when you are providing a default value, which is supported from *Camel 2.14.1* onwards. -### PropertyResolver +=== PropertyResolver Camel provides a pluggable mechanism which allows 3rd part to provide their own resolver to lookup properties. Camel provides a default @@ -146,7 +146,7 @@ prefix is provided) * `blueprint:` *Camel 2.7:* to use a specific OSGi blueprint placeholder service -### Defining location +=== Defining location The `PropertiesResolver` need to know a location(s) where to resolve the properties. You can define 1 to many locations. If you define the @@ -169,7 +169,7 @@ pc.setLocations( "com/mycompany/defaults.properties"); ---- -#### Using system and environment variables in locations +#=== Using system and environment variables in locations *Available as of Camel 2.7* @@ -203,7 +203,7 @@ You can have multiple placeholders in the same location, such as: location=file:${env:APP_HOME}/etc/${prop.name}.properties ---- -#### Using system and environment variables to configure property prefixes and suffixes +#=== Using system and environment variables to configure property prefixes and suffixes *Available as of Camel 2.12.5, 2.13.3, 2.14.0* @@ -240,7 +240,7 @@ property `stage` either to `dev` (the message will be routed to `mock:result1`) or `test` (the message will be routed to `mock:result2`). -### Configuring in Java DSL +=== Configuring in Java DSL You have to create and register the `PropertiesComponent` under the name `properties` such as: @@ -252,7 +252,7 @@ pc.setLocation("classpath:com/mycompany/myprop.properties"); context.addComponent("properties", pc); ---- -### Configuring in Spring XML +=== Configuring in Spring XML Spring XML offers two variations to configure. You can define a spring bean as a `PropertiesComponent` which resembles the way done in Java @@ -302,7 +302,7 @@ Setting the properties location through the location tag works just fine but som Camel 2.10 onwards supports specifying a value for the cache option both inside the Spring as well as the Blueprint XML. -### Using a Properties from the link:registry.html[Registry] +=== Using a Properties from the link:registry.html[Registry] *Available as of Camel 2.4* + For example in OSGi you may want to expose a service which returns the @@ -320,7 +320,7 @@ Where `myProperties` is the id to use for lookup in the OSGi registry. Notice we use the `ref:` prefix to tell Camel that it should lookup the properties for the link:registry.html[Registry]. -### Examples using properties component +=== Examples using properties component When using property placeholders in the endpoint URIs you can either use the `properties:` component or define the placeholders directly in the @@ -370,7 +370,7 @@ location in the given uri using the `locations` option: from("direct:start").to("properties:bar.end?locations=com/mycompany/bar.properties"); ---- -### Examples +=== Examples You can also use property placeholders directly in the endpoint uris without having to use `properties:`. @@ -407,7 +407,7 @@ link:producertemplate.html[ProducerTemplate] for example: template.sendBody("{{cool.start}}", "Hello World"); ---- -### Example with link:simple.html[Simple] language +=== Example with link:simple.html[Simple] language The link:simple.html[Simple] language now also support using property placeholders, for example in the route below: @@ -435,7 +435,7 @@ from("direct:start") .transform().simple("Hi ${body}. ${properties:com/mycompany/bar.properties:bar.quote}."); ---- -### Additional property placeholder supported in Spring XML +=== Additional property placeholder supported in Spring XML The property placeholders is also supported in many of the Camel Spring XML tags such as @@ -447,7 +447,7 @@ The example below has property placeholder in the `<jmxAgent>` tag: You can also define property placeholders in the various attributes on the `<camelContext>` tag such as `trace` as shown here: -### Overriding a property setting using a JVM System Property +=== Overriding a property setting using a JVM System Property *Available as of Camel 2.5* + It is possible to override a property value at runtime using a JVM @@ -484,7 +484,7 @@ System.clearProperty("cool.result"); assertMockEndpointsSatisfied(); ---- -### Using property placeholders for any kind of attribute in the XML DSL +=== Using property placeholders for any kind of attribute in the XML DSL *Available as of Camel 2.7* @@ -511,7 +511,7 @@ In our properties file we have the value defined as stop=true ---- -### Using property placeholder in the Java DSL +=== Using property placeholder in the Java DSL *Available as of Camel 2.7* @@ -519,7 +519,7 @@ Likewise we have added support for defining placeholders in the Java DSL using the new `placeholder` DSL as shown in the following equivalent example: -### Using Blueprint property placeholder with Camel routes +=== Using Blueprint property placeholder with Camel routes *Available as of Camel 2.7* @@ -632,7 +632,7 @@ location="blueprint:myblueprint.placeholder,classpath:myproperties.properties" Each location is separated by comma. -#### Overriding Blueprint property placeholders outside CamelContext +#=== Overriding Blueprint property placeholders outside CamelContext *Available as of Camel 2.10.4* @@ -652,7 +652,7 @@ return value *must* be the `persistence-id` of the `<cm:property-placeholder>` tag, which you define in the blueprint XML file. -#### Using .cfg or .properties file for Blueprint property placeholders +#=== Using .cfg or .properties file for Blueprint property placeholders *Available as of Camel 2.10.4* @@ -680,11 +680,11 @@ placeholders such as: [source] ---- -## this is a comment +== this is a comment greeting=Bye ---- -#### Using .cfg file and overriding properties for Blueprint property placeholders +#=== Using .cfg file and overriding properties for Blueprint property placeholders You can do both as well. Here is a complete example. First we have the Blueprint XML file: @@ -700,7 +700,7 @@ echo=Yay destination=mock:result ---- -### Bridging Spring and Camel property placeholders +=== Bridging Spring and Camel property placeholders *Available as of Camel 2.10* @@ -730,7 +730,7 @@ Notice how the hello bean is using pure Spring property placeholders using the `${ }` notation. And in the Camel routes we use the Camel placeholder notation with `{{` and `}}`. -#### Clashing Spring property placeholders with Camels link:simple.html[Simple] language +#=== Clashing Spring property placeholders with Camels link:simple.html[Simple] language Take notice when using Spring bridging placeholder then the spring `${ }` syntax clashes with the link:simple.html[Simple] in Camel, and therefore @@ -756,7 +756,7 @@ to indicate using the link:simple.html[Simple] language in Camel. An alternative is to configure the `PropertyPlaceholderConfigurer` with `ignoreUnresolvablePlaceholders` option to `true`. -### Overriding properties from Camel test kit +=== Overriding properties from Camel test kit *Available as of Camel 2.10* @@ -785,7 +785,7 @@ instruct Camel to ignore any locations which was not discoverable, for example if you run the unit test, in an environment that does not have access to the location of the properties. -### Using @PropertyInject +=== Using @PropertyInject *Available as of Camel 2.12* @@ -836,7 +836,7 @@ You can also add a default value if the key does not exists, such as: private int timeout; ---- -### Using out of the box functions +=== Using out of the box functions *Available as of Camel 2.14.1* @@ -939,7 +939,7 @@ example to call a service on localhost, maybe for unit testing etc </camelContext> ---- -### Using custom functions +=== Using custom functions *Available as of Camel 2.14.1* @@ -1010,11 +1010,11 @@ To register a custom function from Java code is as shown below:  -### See Also +=== See Also * link:properties.html[Properties] component -### See Also +=== See Also * link:configuring-camel.html[Configuring Camel] * link:component.html[Component] http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/ref-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/ref-component.adoc b/camel-core/src/main/docs/ref-component.adoc index 6411709..4bfdd45 100644 --- a/camel-core/src/main/docs/ref-component.adoc +++ b/camel-core/src/main/docs/ref-component.adoc @@ -5,7 +5,7 @@ The *ref:* component is used for lookup of existing endpoints bound in the link:registry.html[Registry]. -### URI format +=== URI format [source,java] ---------------------- @@ -17,7 +17,7 @@ link:registry.html[Registry] (usually, but not always, the Spring registry). If you are using the Spring registry, `someName` would be the bean ID of an endpoint in the Spring registry. -### Ref Options +=== Ref Options // component options: START The Ref component has no options. @@ -54,7 +54,7 @@ with the following path and query parameters: // endpoint options: END -### Runtime lookup +=== Runtime lookup This component can be used when you need dynamic discovery of endpoints in the link:registry.html[Registry] where you can compute the URI at @@ -86,7 +86,7 @@ link:registry.html[Registry] such as: </camelContext> ---------------------------------------------------------------------------------- -### Sample +=== Sample In the sample below we use the `ref:` in the URI to reference the endpoint with the spring ID, `endpoint2`: @@ -100,7 +100,7 @@ You could, of course, have used the `ref` attribute instead: Which is the more common way to write it. -### See Also +=== See Also * link:configuring-camel.html[Configuring Camel] * link:component.html[Component] http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/ref-language.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/ref-language.adoc b/camel-core/src/main/docs/ref-language.adoc index 924d633..c324c12 100644 --- a/camel-core/src/main/docs/ref-language.adoc +++ b/camel-core/src/main/docs/ref-language.adoc @@ -7,7 +7,7 @@ link:expression.html[Expression] or link:predicate.html[Predicate] from the link This is particular useable in XML DSLs. -### Ref Language options +=== Ref Language options // language options: START The Ref language supports 1 options which are listed below. @@ -21,7 +21,7 @@ The Ref language supports 1 options which are listed below. |=== // language options: END -### Example usage +=== Example usage The link:splitter.html[Splitter] in XML DSL can utilize a custom expression using `<ref>` like: @@ -53,6 +53,6 @@ And the same example using Java DSL: from("seda:a").split().ref("myExpression").to("seda:b"); -------------------------------------------------------- -### Dependencies +=== Dependencies The Ref language is part of *camel-core*. http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/rest-api-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/rest-api-component.adoc b/camel-core/src/main/docs/rest-api-component.adoc index ead367f..eec1fe6 100644 --- a/camel-core/src/main/docs/rest-api-component.adoc +++ b/camel-core/src/main/docs/rest-api-component.adoc @@ -6,7 +6,7 @@ Apache Camel offers a REST styled DSL which can be used with Java or XML. The intention is to allow end users to define REST services using a REST style with verbs such as get, post, delete etc. -### How it works +=== How it works The Rest DSL is a facade that builds link:rest.html[Rest] endpoints as consumers for Camel routes. The actual REST transport is leveraged by @@ -14,7 +14,7 @@ using Camel REST components such as link:restlet.html[Restlet], link:spark-rest.html[Spark-rest], and others that has native REST integration. -### Components supporting Rest DSL +=== Components supporting Rest DSL The following Camel components supports the Rest DSL. See the bottom of this page for how to integrate a component with the Rest DSL. @@ -35,7 +35,7 @@ supports link:swagger-java.html[Swagger Java] from Camel 2.17 onwards) * link:undertow.html[camel-undertow] (also supports link:swagger-java.html[Swagger Java] from Camel 2.17 onwards) -### Rest DSL with Java +=== Rest DSL with Java To use the Rest DSL in Java then just do as with regular Camel routes by extending the `RouteBuilder` and define the routes in the `configure` @@ -85,7 +85,7 @@ routing directly to an endpoint using to(). An alternative is to embed a Camel route directly using route() - there is such an example further below. -### Rest DSL with XML +=== Rest DSL with XML The REST DSL supports the XML DSL also using either Spring or Blueprint. The example above can be define in XML as shown below: @@ -121,7 +121,7 @@ The example above can be define in XML as shown below:  -### Using base path +=== Using base path The REST DSL allows to define base path to make the DSL a bit more DRY. For example to define a customer path, we can set the base path in @@ -179,7 +179,7 @@ only. The example above can be defined as: </rest> ------------------------------------------- -### Using Dynamic To +=== Using Dynamic To *Available as of Camel 2.16* @@ -195,7 +195,7 @@ over link:jms.html[JMS] where the queue name is dynamic defined } ------------------------------------------------------------------------- -### And in XML DSL +=== And in XML DSL [source,xml] --------------------------------------------------- @@ -212,7 +212,7 @@ See more details at link:message-endpoint.html[Message Endpoint] about the dynamic to, and what syntax it supports. By default it uses the link:simple.html[Simple] language, but it has more power than so. -### Embedding Camel routes +=== Embedding Camel routes Each of the rest service becomes a Camel route, so in the first example we have 2 x get and 1 x post REST service, which each become a Camel @@ -259,7 +259,7 @@ today. --------------------------------------------------------------------------------------------- -### Managing Rest services +=== Managing Rest services Each of the rest service becomes a Camel route, so in the first example we have 2 x get and 1 x post REST service, which each become a Camel @@ -274,7 +274,7 @@ performance statistics. There is also a Rest Registry JMX MBean that contains a registry of all REST services which has been defined. -### Binding to POJOs using +=== Binding to POJOs using The Rest DSL supports automatic binding json/xml contents to/from POJOs using Camels link:data-format.html[Data Format]. By default the binding @@ -476,7 +476,7 @@ public class UserPojo { By having the JAXB annotations the POJO supports both json and xml bindings. -### Configuring Rest DSL +=== Configuring Rest DSL // component options: START @@ -538,7 +538,7 @@ example configure 2 component options, and 3 endpoint options etc.  -### Enabling or disabling Jackson JSON features +=== Enabling or disabling Jackson JSON features *Available as of Camel 2.15* @@ -592,7 +592,7 @@ The rest configuration is of course also possible using XML DSL  -### Default CORS headers +=== Default CORS headers *Available as of Camel 2.14.1* @@ -614,7 +614,7 @@ Access-Control-Request-Method, Access-Control-Request-Headers |Access-Control-Max-Age |3600 |=======================================================================  -### Defining a custom error message as-is +=== Defining a custom error message as-is If you want to define custom error messages to be sent back to the client with a HTTP error code (eg such as 400, 404 etc.) then @@ -658,7 +658,7 @@ the HTTP error code to 400. This is important, as that tells rest-dsl that this is a custom error message, and the message should not use the output pojo binding (eg would otherwise bind to CountryPojo). -### Catching JsonParserException and returning a custom error message +=== Catching JsonParserException and returning a custom error message From *Camel 2.14.1* onwards you return a custom message as-is (see previous section). So we can leverage this with Camel error handler to @@ -677,7 +677,7 @@ onException(JsonParseException.class)  -### Query Parameter default Values +=== Query Parameter default Values You can specify default values for parameters in the rest-dsl, such as the verbose parameter below: @@ -699,7 +699,7 @@ key `verbose` then Camel will now include a header with key `verbose` and the value `false` because it was declared as the default value. This functionality is only applicable for query parameters. -### Integrating a Camel component with Rest DSL +=== Integrating a Camel component with Rest DSL Any Apache Camel component can integrate with the Rest DSL if they can be used as a REST service (eg as a REST consumer in Camel lingo). To @@ -711,7 +711,7 @@ Camel consumer that exposes the REST services based on the given parameters, such as path, verb, and other options. For example see the source code for camel-restlet, camel-spark-rest. -### Swagger API +=== Swagger API The Rest DSL supports link:swagger-java.html[Swagger Java] by the `camel-swagger-java` module. See more details at @@ -769,7 +769,7 @@ And in Java DSL For an example see the `examples/camel-example-servlet-rest-tomcat` of the Apache Camel distribution. -### See Also +=== See Also * link:dsl.html[DSL] * link:rest.html[Rest] http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/rest-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/rest-component.adoc b/camel-core/src/main/docs/rest-component.adoc index c677ca7..81265a3 100644 --- a/camel-core/src/main/docs/rest-component.adoc +++ b/camel-core/src/main/docs/rest-component.adoc @@ -8,14 +8,14 @@ REST transport. From Camel 2.18 onwards the rest component can also be used as a client (producer) to call REST services. -### URI format +=== URI format [source,java] -------------------------------------------- rest://method:path[:uriTemplate]?[options] -------------------------------------------- -### URI Options +=== URI Options // component options: START The REST component supports 4 options which are listed below. @@ -74,7 +74,7 @@ with the following path and query parameters: |=== // endpoint options: END -### Supported rest components +=== Supported rest components The following components support rest consumer (link:rest-dsl.html[Rest DSL]): @@ -96,7 +96,7 @@ The following components support rest producer: * camel-restlet * camel-undertow -### Path and uriTemplate syntax +=== Path and uriTemplate syntax The path and uriTemplate option is defined using a REST syntax where you define the REST context path using support for parameters. @@ -135,7 +135,7 @@ have two REST services configured using uriTemplates. .transform().simple("Bonjour ${header.me}"); ------------------------------------------------ -### Rest producer examples +=== Rest producer examples You can use the rest component to call REST services like any other Camel component. @@ -186,7 +186,7 @@ to use http4 you can do: -------------------------------------------- -### Rest producer binding +=== Rest producer binding The REST producer supports binding using JSon or XML like the rest-dsl does. @@ -230,7 +230,7 @@ For example if the REST service returns a JSon payload that binds to `com.foo.My IMPORTANT: You must configure `outType` option if you want POJO binding to happen for the response messages received from calling the REST service. -### More examples +=== More examples See link:rest-dsl.html[Rest DSL] which offers more examples and how you can use the Rest DSL to define those in a nicer RESTful way. @@ -241,7 +241,7 @@ link:rest-dsl.html[Rest DSL] with link:servlet.html[SERVLET] as transport that can be deployed on Apache Tomcat, or similar web containers. -### See Also +=== See Also * link:configuring-camel.html[Configuring Camel] * link:component.html[Component] http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/return-address.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/return-address.adoc b/camel-core/src/main/docs/return-address.adoc index 2ad9884..536b2c4 100644 --- a/camel-core/src/main/docs/return-address.adoc +++ b/camel-core/src/main/docs/return-address.adoc @@ -1,4 +1,4 @@ -## Return Address +== Return Address Camel supports the http://www.enterpriseintegrationpatterns.com/ReturnAddress.html[Return @@ -55,7 +55,7 @@ test case] [[ReturnAddress-UsingThisPattern]] -### Using This Pattern +=== Using This Pattern If you would like to use this EIP Pattern then please read the link:getting-started.html[Getting Started], you may also find the http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/scheduler-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/scheduler-component.adoc b/camel-core/src/main/docs/scheduler-component.adoc index c681180..3cf2be0 100644 --- a/camel-core/src/main/docs/scheduler-component.adoc +++ b/camel-core/src/main/docs/scheduler-component.adoc @@ -10,7 +10,7 @@ JDK `ScheduledExecutorService`. Where as the timer uses a JDK `Timer`. You can only consume events from this endpoint. -### URI format +=== URI format [source,java] ------------------------ @@ -28,7 +28,7 @@ You can append query options to the URI in the following format, *Note:* The IN body of the generated exchange is `null`. So `exchange.getIn().getBody()` returns `null`. -### Options +=== Options // component options: START The Scheduler component supports 2 options which are listed below. @@ -90,7 +90,7 @@ with the following path and query parameters: // endpoint options: END -### More information +=== More information This component is a scheduler http://camel.apache.org/polling-consumer.html[Polling Consumer] where @@ -98,7 +98,7 @@ you can find more information about the options above, and examples at the http://camel.apache.org/polling-consumer.html[Polling Consumer] page. -### Exchange Properties +=== Exchange Properties When the timer is fired, it adds the following information as properties to the `Exchange`: @@ -112,7 +112,7 @@ to the `Exchange`: |`Exchange.TIMER_FIRED_TIME` |`Date` |The time when the consumer fired. |======================================================================= -### Sample +=== Sample To set up a route that generates an event every 60 seconds: @@ -139,13 +139,13 @@ And the route in Spring DSL:  -### Forcing the scheduler to trigger immediately when completed +=== Forcing the scheduler to trigger immediately when completed To let the scheduler trigger as soon as the previous task is complete, you can set the option greedy=true. But beware then the scheduler will keep firing all the time. So use this with caution. -### Forcing the scheduler to be idle +=== Forcing the scheduler to be idle There can be use cases where you want the scheduler to trigger and be greedy. But sometimes you want "tell the scheduler" that there was no @@ -161,7 +161,7 @@ exchange.  -### See Also +=== See Also * link:configuring-camel.html[Configuring Camel] * link:component.html[Component] http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/seda-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/seda-component.adoc b/camel-core/src/main/docs/seda-component.adoc index 137b458..e74494a 100644 --- a/camel-core/src/main/docs/seda-component.adoc +++ b/camel-core/src/main/docs/seda-component.adoc @@ -22,7 +22,7 @@ TIP:*Synchronous* The link:direct.html[Direct] component provides synchronous invocation of any consumers when a producer sends a message exchange. -### URI format +=== URI format [source,java] ----------------------- @@ -35,7 +35,7 @@ within the current link:camelcontext.html[CamelContext]. You can append query options to the URI in the following format: `?option=value&option=value&â¦` -### Options +=== Options // component options: START The SEDA component supports 4 options which are listed below. @@ -95,7 +95,7 @@ with the following path and query parameters: // endpoint options: END -### Choosing BlockingQueue implementation +=== Choosing BlockingQueue implementation *Available as of Camel 2.12* @@ -128,7 +128,7 @@ ArrayBlockingQueueFactory and PriorityBlockingQueueFactory: <from>seda:priority?queueFactory=#priorityQueueFactory&size=100</from> ----------------------------------------------------------------------------------------------------- -### Use of Request Reply +=== Use of Request Reply The link:seda.html[SEDA] component supports using link:request-reply.html[Request Reply], where the caller will wait for @@ -157,7 +157,7 @@ between the waiting threads properly. This has been improved in *Camel 2.3* onwards, which allows you to chain as many endpoints as you like. -### Concurrent consumers +=== Concurrent consumers By default, the SEDA endpoint uses a single consumer thread, but you can configure it to use concurrent consumer threads. So instead of thread @@ -172,7 +172,7 @@ As for the difference between the two, note a _thread pool_ can increase/shrink dynamically at runtime depending on load, whereas the number of concurrent consumers is always fixed. -### Thread pools +=== Thread pools Be aware that adding a thread pool to a SEDA endpoint by doing something like: @@ -196,7 +196,7 @@ from("direct:stageName").thread(5).process(...) You can also directly configure number of threads that process messages on a SEDA endpoint using the `concurrentConsumers` option. -### Sample +=== Sample In the route below we use the SEDA queue to send the request to this async queue to be able to send a fire-and-forget message for further @@ -210,7 +210,7 @@ another thread for further processing. Since this is from a unit test, it will be sent to a `mock` endpoint where we can do assertions in the unit test. -### Using multipleConsumers +=== Using multipleConsumers *Available as of Camel 2.2* @@ -225,7 +225,7 @@ As the beans are part of an unit test they simply send the message to a mock endpoint, but notice how we can use @Consume to consume from the seda queue. -### Extracting queue information. +=== Extracting queue information. If needed, information such as queue size, etc. can be obtained without using JMX in this fashion: @@ -236,7 +236,7 @@ SedaEndpoint seda = context.getEndpoint("seda:xxxx"); int size = seda.getExchanges().size(); ----------------------------------------------------- -### See Also +=== See Also * link:configuring-camel.html[Configuring Camel] * link:component.html[Component] http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/serialization-dataformat.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/serialization-dataformat.adoc b/camel-core/src/main/docs/serialization-dataformat.adoc index 739e326..2025de8 100644 --- a/camel-core/src/main/docs/serialization-dataformat.adoc +++ b/camel-core/src/main/docs/serialization-dataformat.adoc @@ -15,7 +15,7 @@ from("file://foo/bar"). to("activemq:Some.Queue"); ------------------------------ -### Options +=== Options // dataformat options: START The Java Object Serialization dataformat supports 1 options which are listed below. @@ -29,7 +29,7 @@ The Java Object Serialization dataformat supports 1 options which are listed bel |=== // dataformat options: END -### Dependencies +=== Dependencies This data format is provided in *camel-core* so no additional dependencies is needed. http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/simple-language.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/simple-language.adoc b/camel-core/src/main/docs/simple-language.adoc index 5207f3d..c60cd9f 100644 --- a/camel-core/src/main/docs/simple-language.adoc +++ b/camel-core/src/main/docs/simple-language.adoc @@ -78,7 +78,7 @@ You can have multiple functions in the same expression: having another $\{ } placeholder in an existing, is not allowed). + From *Camel 2.9* onwards you can nest functions. -### Simple Language options +=== Simple Language options // language options: START The Simple language supports 2 options which are listed below. @@ -93,7 +93,7 @@ The Simple language supports 2 options which are listed below. |=== // language options: END -### Variables +=== Variables [width="100%",cols="10%,10%,80%",options="header",] |======================================================================= @@ -286,7 +286,7 @@ includes the route strack-trace). This can be used if you do not want to log sensitive data from the message itself. |======================================================================= -### OGNL expression support +=== OGNL expression support *Available as of Camel 2.3* @@ -421,7 +421,7 @@ And yes you can combine this with the operator support as shown below: simple("${body.address.zip} > 1000") ------------------------------------ -### Operator support +=== Operator support The parser is limited to only support a single operator. @@ -721,7 +721,7 @@ order: </from> ------------------------------------------------------------ -#### Using and / or +#=== Using and / or If you have two expressions you can combine them with the `and` or `or` operator. @@ -753,7 +753,7 @@ language expression. This might change in the future. + simple("${in.header.title} contains 'Camel' and ${in.header.type'} == 'gold' and ${in.header.number} range 100..200") --------------------------------------------------------------------------------------------------------------------- -### Samples +=== Samples In the Spring XML sample below we filter based on a header value: @@ -868,7 +868,7 @@ From Camel 2.9 onwards you can nest functions, such as shown below: </setHeader> -------------------------------------------------- -#### Referring to constants or enums +#=== Referring to constants or enums *Available as of Camel 2.11* @@ -878,7 +878,7 @@ And in a link:content-based-router.html[Content Based Router] we can use the link:simple.html[Simple] language to refer to this enum, to check the message which enum it matches. -### Using new lines or tabs in XML DSLs +=== Using new lines or tabs in XML DSLs *Available as of Camel 2.9.3* @@ -892,7 +892,7 @@ XML DSLs as you can escape the value now </transform> ------------------------------------------------------- -### Leading and trailing whitespace handling +=== Leading and trailing whitespace handling *Available as of Camel 2.10.0* @@ -908,7 +908,7 @@ whitespace characters. </setBody> --------------------------------------------------------------------------------- -### Setting result type +=== Setting result type *Available as of Camel 2.8* @@ -934,7 +934,7 @@ And in XML DSL </setHeader> --------------------------------------------------------------------------------------- -### Changing function start and end tokens +=== Changing function start and end tokens *Available as of Camel 2.9.1* @@ -959,7 +959,7 @@ applications which share the same *camel-core* on their classpath. + For example in an OSGi server this may affect many applications, where as a Web Application as a WAR file it only affects the Web Application. -### Loading script from external resource +=== Loading script from external resource *Available as of Camel 2.11* @@ -973,7 +973,7 @@ eg to refer to a file on the classpath you can do: .setHeader("myHeader").simple("resource:classpath:mysimple.txt") ---------------------------------------------------------------- -### Setting Spring beans to Exchange properties +=== Setting Spring beans to Exchange properties *Available as of Camel 2.6* @@ -992,6 +992,6 @@ You can set a spring bean into an exchange property as shown below: </route> ------------------------------------------------------- -### Dependencies +=== Dependencies The link:simple.html[Simple] language is part of *camel-core*. http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/string-dataformat.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/string-dataformat.adoc b/camel-core/src/main/docs/string-dataformat.adoc index d4ea7b3..0ef323d 100644 --- a/camel-core/src/main/docs/string-dataformat.adoc +++ b/camel-core/src/main/docs/string-dataformat.adoc @@ -5,7 +5,7 @@ The String link:data-format.html[Data Format] is a textual based format that supports encoding. -### Options +=== Options // dataformat options: START The String Encoding dataformat supports 2 options which are listed below. @@ -20,7 +20,7 @@ The String Encoding dataformat supports 2 options which are listed below. |=== // dataformat options: END -### Marshal +=== Marshal In this example we marshal the file content to String object in UTF-8 encoding. @@ -30,7 +30,7 @@ encoding. from("file://data.csv").marshal().string("UTF-8").to("jms://myqueue"); ---------------------------------------------------------------------- -### Unmarshal +=== Unmarshal In this example we unmarshal the payload from the JMS queue to a String object using UTF-8 encoding, before its processed by the newOrder @@ -41,7 +41,7 @@ processor. from("jms://queue/order").unmarshal().string("UTF-8").processRef("newOrder"); ----------------------------------------------------------------------------- -### Dependencies +=== Dependencies This data format is provided in *camel-core* so no additional dependencies is needed. http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/stub-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/stub-component.adoc b/camel-core/src/main/docs/stub-component.adoc index 00d7443..e543150 100644 --- a/camel-core/src/main/docs/stub-component.adoc +++ b/camel-core/src/main/docs/stub-component.adoc @@ -16,7 +16,7 @@ usually fail. Stub won't though, as it basically ignores all query parameters to let you quickly stub out one or more endpoints in your route temporarily. -### URI format +=== URI format [source,java] ------------ @@ -25,7 +25,7 @@ stub:someUri Where *`someUri`* can be any URI with any query parameters. -### Options +=== Options // component options: START The Stub component supports 4 options which are listed below. @@ -85,7 +85,7 @@ with the following path and query parameters: // endpoint options: END -### Examples +=== Examples Here are a few samples: @@ -93,7 +93,7 @@ Here are a few samples: * stub:http://somehost.bar.com/something[http://somehost.bar.com/something] -### See Also +=== See Also * link:configuring-camel.html[Configuring Camel] * link:component.html[Component] http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/test-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/test-component.adoc b/camel-core/src/main/docs/test-component.adoc index 01501b1..ff7b07a 100644 --- a/camel-core/src/main/docs/test-component.adoc +++ b/camel-core/src/main/docs/test-component.adoc @@ -39,7 +39,7 @@ for this component when using *Camel 2.8* or older: From Camel 2.9 onwards the link:test.html[Test] component is provided directly in the camel-core. -### URI format +=== URI format [source,java] -------------------------------- @@ -50,7 +50,7 @@ Where *expectedMessagesEndpointUri* refers to some other link:component.html[Component] URI that the expected message bodies are pulled from before starting the test. -### URI Options +=== URI Options // component options: START The Test component has no options. @@ -97,7 +97,7 @@ with the following path and query parameters: // endpoint options: END -### Example +=== Example For example, you could write a test case as follows: @@ -114,7 +114,7 @@ method], your test case will perform the necessary assertions. To see how you can set other expectations on the test endpoint, see the link:mock.html[Mock] component. -### See Also +=== See Also * link:configuring-camel.html[Configuring Camel] * link:component.html[Component] http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/timer-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/timer-component.adoc b/camel-core/src/main/docs/timer-component.adoc index 6925a76..e1e04ac 100644 --- a/camel-core/src/main/docs/timer-component.adoc +++ b/camel-core/src/main/docs/timer-component.adoc @@ -5,7 +5,7 @@ The *timer:* component is used to generate message exchanges when a timer fires You can only consume events from this endpoint. -### URI format +=== URI format [source,java] -------------------- @@ -32,7 +32,7 @@ link:how-do-i-specify-time-period-in-a-human-friendly-syntax.html[human friendly syntax]. -### Options +=== Options // component options: START The Timer component has no options. @@ -77,7 +77,7 @@ with the following path and query parameters: // endpoint options: END -### Exchange Properties +=== Exchange Properties When the timer is fired, it adds the following information as properties to the `Exchange`: @@ -97,7 +97,7 @@ to the `Exchange`: |`Exchange.TIMER_COUNTER` |`Long` |*Camel 2.8:* The current fire counter. Starts from 1. |======================================================================= -### Sample +=== Sample To set up a route that generates an event every 60 seconds: @@ -122,9 +122,9 @@ And the route in Spring DSL: </route> ------------------------------------------------------------- -#### Firing as soon as possible +#=== Firing as soon as possible -#### Available as of Camel 2.17 +#=== Available as of Camel 2.17 You may want to fire messages in a Camel route as soon as possible you can use a negative delay: @@ -146,7 +146,7 @@ reached. If you don't specify a repeatCount then the timer will continue firing messages until the route will be stopped. -#### Firing only once +#=== Firing only once *Available as of Camel 2.8* @@ -161,7 +161,7 @@ starting the route. To do that you use the repeatCount option as shown: </route> ------------------------------------------------- -### See Also +=== See Also * link:configuring-camel.html[Configuring Camel] * link:component.html[Component] http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/tokenize-language.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/tokenize-language.adoc b/camel-core/src/main/docs/tokenize-language.adoc index 303ac72..b9fe05d 100644 --- a/camel-core/src/main/docs/tokenize-language.adoc +++ b/camel-core/src/main/docs/tokenize-language.adoc @@ -13,7 +13,7 @@ language is recommended as it offers a faster, more efficient tokenization specifically for XML documents. For more details see link:splitter.html[Splitter]. -### Tokenize Options +=== Tokenize Options // language options: START The Tokenize language supports 10 options which are listed below. http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/validator-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/validator-component.adoc b/camel-core/src/main/docs/validator-component.adoc index 4523a2c..7285591 100644 --- a/camel-core/src/main/docs/validator-component.adoc +++ b/camel-core/src/main/docs/validator-component.adoc @@ -17,7 +17,7 @@ Syntax] The link:msv.html[MSV] component also supports http://relaxng.org/[RelaxNG XML Syntax]. -### URI format +=== URI format [source,java] ----------------------------------- @@ -49,7 +49,7 @@ for this component when using *Camel 2.8* or older: From Camel 2.9 onwards the link:validation.html[Validation] component is provided directly in the camel-core. -### Options +=== Options // component options: START The Validator component supports 2 options which are listed below. @@ -102,7 +102,7 @@ with the following path and query parameters: // endpoint options: END -### Example +=== Example The following http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/component/validator/camelContext.xml[example] @@ -111,7 +111,7 @@ goes to one of two endpoints, either *mock:valid* or *mock:invalid* based on whether or not the XML matches the given schema (which is supplied on the classpath). -### Advanced: JMX method clearCachedSchema +=== Advanced: JMX method clearCachedSchema Since *Camel 2.17*, you can force that the cached schema in the validator endpoint is cleared and reread with the next process call with @@ -119,7 +119,7 @@ the JMX operation `clearCachedSchema. `You can also use this method to programmatically clear the cache. This method is available on the `ValidatorEndpoint `class`.` -### See Also +=== See Also * link:configuring-camel.html[Configuring Camel] * link:component.html[Component] http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/vm-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/vm-component.adoc b/camel-core/src/main/docs/vm-component.adoc index 96cf525..d81844e 100644 --- a/camel-core/src/main/docs/vm-component.adoc +++ b/camel-core/src/main/docs/vm-component.adoc @@ -15,7 +15,7 @@ this mechanism to communicate across web applications (provided that VM is an extension to the link:seda.html[Seda] component. -### URI format +=== URI format [source,java] ---------------------- @@ -58,7 +58,7 @@ from("direct:foo").to("vm:bar"); from("vm:bar?concurrentConsumers=5").to("file://output"); --------------------------------------------------------- -### Options +=== Options // component options: START The VM component supports 4 options which are listed below. @@ -121,7 +121,7 @@ with the following path and query parameters: See the link:seda.html[Seda] component for options and other important usage details as the same rules apply to the link:vm.html[Vm] component. -### Samples +=== Samples In the route below we send exchanges across CamelContext instances to a VM queue named `order.email`: @@ -139,7 +139,7 @@ deployed in another `.war` application): from("vm:order.email").bean(MyOrderEmailSender.class); ------------------------------------------------------ -### See Also +=== See Also * link:configuring-camel.html[Configuring Camel] * link:component.html[Component] http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/xpath-language.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/xpath-language.adoc b/camel-core/src/main/docs/xpath-language.adoc index a513354..f3cedbf 100644 --- a/camel-core/src/main/docs/xpath-language.adoc +++ b/camel-core/src/main/docs/xpath-language.adoc @@ -35,7 +35,7 @@ from("queue:foo"). otherwise().to("queue:others"); ------------------------------------------- -### XPath Language options +=== XPath Language options // language options: START The XPath language supports 8 options which are listed below. @@ -56,12 +56,12 @@ The XPath language supports 8 options which are listed below. |=== // language options: END -### Namespaces +=== Namespaces You can easily use namespaces with XPath expressions using the Namespaces helper class. -### Variables +=== Variables Variables in XPath is defined in different namespaces. The default namespace is `http://camel.apache.org/schema/spring`. @@ -88,14 +88,14 @@ Camel will resolve variables according to either: * namespace given * no namespace given -#### Namespace given +#=== Namespace given If the namespace is given then Camel is instructed exactly what to return. However when resolving either *in* or *out* Camel will try to resolve a header with the given local part first, and return it. If the local part has the value *body* then the body is returned instead. -#### No namespace given +#=== No namespace given If there is no namespace given then Camel resolves only based on the local part. Camel will try to resolve a variable in the following steps: @@ -105,7 +105,7 @@ fluent builder * from message.in.header if there is a header with the given key * from exchange.properties if there is a property with the given key -### Functions +=== Functions Camel adds the following XPath functions that can be used to access the exchange: @@ -136,7 +136,7 @@ Here's an example showing some of these functions in use. And the new functions introduced in Camel 2.5: -### Using XML configuration +=== Using XML configuration If you prefer to configure your routes in your link:spring.html[Spring] XML file then you can use XPath expressions as follows @@ -168,7 +168,7 @@ See also this http://camel.465427.n5.nabble.com/fail-filter-XPATH-camel-td476424.html[discussion on the mailinglist] about using your own namespaces with xpath -### Setting result type +=== Setting result type The link:xpath.html[XPath] expression will return a result type using native XML objects such as `org.w3c.dom.NodeList`. But many times you @@ -202,7 +202,7 @@ Where we use the xpath function concat to prefix the order name with `foo-`. In this case we have to specify that we want a String as result type so the concat function works. -### Using XPath on Headers +=== Using XPath on Headers *Available as of Camel 2.11* @@ -219,7 +219,7 @@ shown: xpath("/invoice/@orderType = 'premium'", "invoiceDetails") ------------------------------------------------------------ -### Examples +=== Examples Here is a simple http://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/XPathFilterTest.java[example] @@ -240,7 +240,7 @@ which values is *Kong*. + And the spring XML equivalent of the route: -### XPath injection +=== XPath injection You can use link:bean-integration.html[Bean Integration] to invoke a method on a bean and use various languages such as XPath to extract a @@ -271,7 +271,7 @@ public class Foo { } ---------------------------------------------------------------------------------------------------------- -### Using XPathBuilder without an Exchange +=== Using XPathBuilder without an Exchange *Available as of Camel 2.3* @@ -311,7 +311,7 @@ do it a bit simpler: String name = XPathBuilder.xpath("foo/bar").evaluate(context, "<foo><bar>cheese</bar></foo>"); -------------------------------------------------------------------------------------------------- -### Using Saxon with XPathBuilder +=== Using Saxon with XPathBuilder *Available as of Camel 2.3* @@ -327,7 +327,7 @@ Using ObjectModel The easy one -### Setting a custom XPathFactory using System Property +=== Setting a custom XPathFactory using System Property *Available as of Camel 2.3* @@ -354,7 +354,7 @@ To use Apache Xerces you can configure the system property -Djavax.xml.xpath.XPathFactory=org.apache.xpath.jaxp.XPathFactoryImpl --------------------------------------------------------------------- -### Enabling Saxon from Spring DSL +=== Enabling Saxon from Spring DSL *Available as of Camel 2.10* @@ -382,7 +382,7 @@ Shortcut <xpath saxon="true" resultType="java.lang.String">current-dateTime()</xpath> ---------------------------------------------------------------------------- -### Namespace auditing to aid debugging +=== Namespace auditing to aid debugging *Available as of Camel 2.10* @@ -403,7 +403,7 @@ Therefore, the utmost we can do is assist you in debugging such issues by adding two new features to the XPath Expression Language and are thus accesible from both predicates and expressions. -#### Logging the Namespace Context of your XPath expression/predicate +#=== Logging the Namespace Context of your XPath expression/predicate Every time a new XPath expression is created in the internal pool, Camel will log the namespace context of the expression under the @@ -426,7 +426,7 @@ logger such as `org.apache.camel` or the root logger link:xpath.html[Auditing Namespaces], in which case the logging will occur on the INFO level -#### Auditing namespaces +#=== Auditing namespaces Camel is able to discover and dump all namespaces present on every incoming message before evaluating an XPath expression, providing all @@ -476,7 +476,7 @@ the following: xmlns:b=[http://apache.org/camelA, http://apache.org/camelB]} -------------------------------------------------------------------------------------------------- -### Loading script from external resource +=== Loading script from external resource *Available as of Camel 2.11* @@ -490,6 +490,6 @@ eg to refer to a file on the classpath you can do: .setHeader("myHeader").xpath("resource:classpath:myxpath.txt", String.class) ---------------------------------------------------------------------------- -### Dependencies +=== Dependencies The XPath language is part of camel-core. http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/xslt-component.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/xslt-component.adoc b/camel-core/src/main/docs/xslt-component.adoc index 8d74536..c1c309c 100644 --- a/camel-core/src/main/docs/xslt-component.adoc +++ b/camel-core/src/main/docs/xslt-component.adoc @@ -6,7 +6,7 @@ The *xslt:* component allows you to process a message using an http://www.w3.org/TR/xslt[XSLT] template. This can be ideal when using link:templating.html[Templating] to generate respopnses for requests. -### URI format +=== URI format [source,java] --------------------------- @@ -64,7 +64,7 @@ for this component when using *Camel 2.8* or older: From Camel 2.9 onwards the link:xslt.html[XSLT] component is provided directly in the camel-core. -### Options +=== Options // component options: START The XSLT component supports 9 options which are listed below. @@ -130,7 +130,7 @@ with the following path and query parameters: // endpoint options: END -### Using XSLT endpoints +=== Using XSLT endpoints For example you could use something like @@ -153,7 +153,7 @@ from("activemq:My.Queue"). to("activemq:Another.Queue"); -------------------------------------- -### Getting Parameters into the XSLT to work with +=== Getting Parameters into the XSLT to work with By default, all headers are added as parameters which are available in the XSLT. + @@ -178,7 +178,7 @@ available: <xsl:template ...> ------------------------------ -### Spring XML versions +=== Spring XML versions To use the above examples in Spring XML you would use something like @@ -199,7 +199,7 @@ case] along with http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/spring/processor/XsltTest-context.xml[its Spring XML] if you want a concrete example. -### Using xsl:include +=== Using xsl:include *Camel 2.2 or older* + If you use xsl:include in your XSL files then in Camel 2.2 or older it @@ -257,7 +257,7 @@ You can also refer back in the paths such as Which then will resolve the xsl file under `org/apache/camel/component`. -#### Using xsl:include and default prefix +#=== Using xsl:include and default prefix When using xsl:include such as: @@ -298,7 +298,7 @@ the endpoint was configured with "file:" as prefix. + match. And have both file and classpath loading. But that would be unusual, as most people either use file or classpath based resources. -### Using Saxon extension functions +=== Using Saxon extension functions Since Saxon 9.2, writing extension functions has been supplemented by a new mechanism, referred to @@ -347,7 +347,7 @@ Spring example:  -### Dynamic stylesheets +=== Dynamic stylesheets To provide a dynamic stylesheet at runtime you can define a dynamic URI. See link:how-to-use-a-dynamic-uri-in-to.html[How to use a dynamic URI in @@ -358,7 +358,7 @@ to()] for more information. define a stylesheet to use instead of what is configured on the endpoint URI. This allows you to provide a dynamic stylesheet at runtime. -### Accessing warnings, errors and fatalErrors from XSLT ErrorListener +=== Accessing warnings, errors and fatalErrors from XSLT ErrorListener *Available as of Camel 2.14* @@ -394,7 +394,7 @@ that contains the message in the `getMessage()` method on the exception. The exception is stored on the Exchange as a warning with the key `Exchange.XSLT_WARNING.` -### Notes on using XSLT and Java Versions +=== Notes on using XSLT and Java Versions Here are some observations from Sameer, a Camel user, which he kindly shared with us: @@ -435,7 +435,7 @@ for the jvm or as specified by the container. Hope this post saves newbie Camel riders some time. ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ -### See Also +=== See Also * link:configuring-camel.html[Configuring Camel] * link:component.html[Component] http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/xtokenize-language.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/xtokenize-language.adoc b/camel-core/src/main/docs/xtokenize-language.adoc index 53cb9bc..d799646 100644 --- a/camel-core/src/main/docs/xtokenize-language.adoc +++ b/camel-core/src/main/docs/xtokenize-language.adoc @@ -12,7 +12,7 @@ Tokenizer. For more details see link:splitter.html[Splitter]. -### XML Tokenizer Options +=== XML Tokenizer Options // language options: START The XML Tokenize language supports 4 options which are listed below. http://git-wip-us.apache.org/repos/asf/camel/blob/9f22fab8/camel-core/src/main/docs/zip-dataformat.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/zip-dataformat.adoc b/camel-core/src/main/docs/zip-dataformat.adoc index 30e8be6..67b7c19 100644 --- a/camel-core/src/main/docs/zip-dataformat.adoc +++ b/camel-core/src/main/docs/zip-dataformat.adoc @@ -16,7 +16,7 @@ Which means that when using big files, the entire file content is loaded into memory. This is subject to change in the future, to allow a streaming based solution to have a low memory footprint. -### Options +=== Options // dataformat options: START The Zip Deflate Compression dataformat supports 2 options which are listed below. @@ -31,7 +31,7 @@ The Zip Deflate Compression dataformat supports 2 options which are listed below |=== // dataformat options: END -### Marshal +=== Marshal In this example we marshal a regular text/XML payload to a compressed payload employing zip compression `Deflater.BEST_COMPRESSION` and send @@ -50,7 +50,7 @@ send it as from("direct:start").marshal().zip().to("activemq:queue:MY_QUEUE"); ------------------------------------------------------------------- -### Unmarshal +=== Unmarshal In this example we unmarshal a zipped payload from an ActiveMQ queue called MY_QUEUE to its original format, and forward it for processing to @@ -63,7 +63,7 @@ unmarshalling to avoid errors. from("activemq:queue:MY_QUEUE").unmarshal().zip().process(new UnZippedMessageProcessor()); ------------------------------------------------------------------------------------------- -### Dependencies +=== Dependencies This data format is provided in *camel-core* so no additional dependencies are needed.
