[camel] branch master updated: Update log-eip.adoc

[ac...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/master by this push:
     new 1a55f37  Update log-eip.adoc
1a55f37 is described below

commit 1a55f378067edd5577112121f01bc95eed1188c7
Author: Mikael Andersson Wigander <mi...@pm.me>
AuthorDate: Thu Oct 1 10:42:17 2020 +0200

    Update log-eip.adoc
    
    Adding link to FAQ for logging message bodys in streamed messages
---
 core/camel-core-engine/src/main/docs/modules/eips/pages/log-eip.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/core/camel-core-engine/src/main/docs/modules/eips/pages/log-eip.adoc b/core/camel-core-engine/src/main/docs/modules/eips/pages/log-eip.adoc
index 26c2817f..95f399a 100644
--- a/core/camel-core-engine/src/main/docs/modules/eips/pages/log-eip.adoc
+++ b/core/camel-core-engine/src/main/docs/modules/eips/pages/log-eip.adoc
@@ -52,7 +52,7 @@ Which will construct a String message at runtime using the Simple language. The
 ====
 *Logging message body with streamed messages:*
 
-If the message body is stream based, then logging the message body, may cause the message body to be empty afterwards. See this FAQ. For streamed messages you can use Stream caching to allow logging the message body and be able to read the message body afterwards again.
+If the message body is stream based, then logging the message body, may cause the message body to be empty afterwards. See this https://camel.apache.org/manual/latest/faq/why-is-my-message-body-empty.html[FAQ]. For streamed messages you can use Stream caching to allow logging the message body and be able to read the message body afterwards again.
 ====
 
 The log DSL have overloaded methods to set the logging level and/or name as well.