This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 67763ac15eda CAMEL-16861: Cleanup docs
67763ac15eda is described below
commit 67763ac15edaad6ab39642d567da781475382ef5
Author: Claus Ibsen <[email protected]>
AuthorDate: Thu Mar 5 19:20:54 2026 +0100
CAMEL-16861: Cleanup docs
---
.../camel-seda/src/main/docs/seda-component.adoc | 4 +-
docs/user-manual/modules/ROOT/pages/endpoint.adoc | 102 +++++++++++++++++++++
docs/user-manual/modules/ROOT/pages/tracer.adoc | 44 +++++++++
docs/user-manual/modules/faq/nav.adoc | 8 --
...-contexttestsupport-class-in-my-unit-tests.adoc | 7 --
...chars-when-debug-logging-messages-in-camel.adoc | 53 -----------
...do-i-set-the-mep-when-interacting-with-jbi.adoc | 33 -------
...ify-time-period-in-a-human-friendly-syntax.adoc | 54 -----------
...h-method-to-use-when-using-beans-in-routes.adoc | 8 --
.../how-do-i-use-uris-with-parameters-in-xml.adoc | 50 ----------
...om-processor-which-sends-multiple-messages.adoc | 50 ----------
...direct-event-seda-and-vm-endpoints-compare.adoc | 15 ---
...-do-the-timer-and-quartz-endpoints-compare.adoc | 7 --
docs/user-manual/modules/faq/pages/index.adoc | 20 ----
14 files changed, 148 insertions(+), 307 deletions(-)
diff --git a/components/camel-seda/src/main/docs/seda-component.adoc
b/components/camel-seda/src/main/docs/seda-component.adoc
index 112a28bb6686..36a5735118eb 100644
--- a/components/camel-seda/src/main/docs/seda-component.adoc
+++ b/components/camel-seda/src/main/docs/seda-component.adoc
@@ -34,8 +34,8 @@ If you need persistence, reliability or distributed SEDA, try
using xref:jms-com
====
*Synchronous*
-The xref:direct-component.adoc[Direct] component provides synchronous
invocation
-of any consumers when a producer sends a message exchange.
+The xref:direct-component.adoc[Direct] component provides synchronous
invocation (uses no threading; it directly invokes the
+consumer when sending) of any consumers when a producer sends a message
exchange.
====
== URI format
diff --git a/docs/user-manual/modules/ROOT/pages/endpoint.adoc
b/docs/user-manual/modules/ROOT/pages/endpoint.adoc
index f73805fb9458..08d0283f20b9 100644
--- a/docs/user-manual/modules/ROOT/pages/endpoint.adoc
+++ b/docs/user-manual/modules/ROOT/pages/endpoint.adoc
@@ -126,6 +126,58 @@ in the xref:registry.adoc[Registry] that the file endpoint
should use.
file://inbox?idempontentRepository=#type:org.apache.camel.spi.IdempotentRepository
----
+=== Configuring endpoint URIs in XML escaping & sign
+
+If you try and use one of the Camel xref:ROOT:uris.adoc[URIs] in an
+XML DSL using the URI query parameter notation, such as:
+
+[source,xml]
+----
+<route>
+ <from uri="direct:start?paramA=1¶mB=2"/>
+ <to uri="mock:result"/>
+</route>
+----
+
+you might get errors such as...
+
+----
+Caused by: org.xml.sax.SAXParseException: The reference to entity "paramB"
must end with the ';' delimiter.
+ at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
+ at
+----
+
+This is because in XML you need to escape some special XML characters
+like these:
+
+[width="100%",cols="50%,50%",options="header",]
+|==================================================
+|Special Character |How to escape it in XML
+a|`&`
+
+a|`+&+`
+
+a|`<`
+
+a|`+<+`
+
+a|`>`
+
+a|`+>+`
+
+|==================================================
+
+So if you write the following XML it should work...
+
+[source,xml]
+----
+<route>
+ <from uri="direct:start?paramA=1&paramB=2"/>
+ <to uri="mock:result"/>
+</route>
+----
+
+
=== Configuring parameter values using raw values, such as passwords
When configuring endpoint options using URI syntax, then the values is
@@ -322,6 +374,56 @@ The default maximum cache size is 1000.
You need to configure this before xref:ROOT:camelcontext.adoc[CamelContext] is
started.
+== Configuring time duration using hours, minutes syntax
+
+Some of the Camel xref:ROOT:component.adoc[components] offers options to
+specify a time period, which must be entered in millisecond as unit.
+
+This may be unfriendly to read as a human when the value is large such
+as `2700000` millis (45 minutes).
+
+In Camel you can configure this in a more readable syntax as explained:
+
+[width="100%",cols="50%,50%",options="header",]
+|============
+|Syntax |Unit
+|h |hour
+|m |minute
+|s |second
+|============
+
+So for example the xref:components::timer-component.adoc[Timer] endpoint can
be configured as
+follows:
+
+[source,java]
+----
+from("timer:foo?period=45m").to("log:foo");
+----
+
+You can mix and match the units so you can do this as well:
+
+[source,java]
+----
+from("timer:foo?period=1h15m").to("log:foo");
+from("timer:bar?period=2h30s").to("log:bar");
+from("timer:bar?period=3h45m58s").to("log:bar");
+----
+
+However, you can also use long syntax:
+
+[width="100%",cols="50%,50%",options="header",]
+|=========================
+|Syntax |Unit
+|hour _or_ hours |hour
+|minute _or_ minutes |minute
+|second _or_ seconds |second
+|=========================
+
+[source,java]
+----
+from("timer:foo?period=45minutes").to("log:foo");
+----
+
== Java Endpoint API
diff --git a/docs/user-manual/modules/ROOT/pages/tracer.adoc
b/docs/user-manual/modules/ROOT/pages/tracer.adoc
index 19f5ad0f62af..5b42ae28f3fd 100644
--- a/docs/user-manual/modules/ROOT/pages/tracer.adoc
+++ b/docs/user-manual/modules/ROOT/pages/tracer.adoc
@@ -137,6 +137,50 @@ camel.main.tracing-logging-format = %-4.4s [%-30.30s]
[%-50.50s]
----
====
+=== Configuring maximum length of message body
+
+When you run Camel with logging, it will log the messages and its
+content from time to time.
+
+As some messages can contain very big payloads Camel will by default
+clip the log message and only show the first 1000 chars.
+
+You will see this in the log as:
+
+[source,log]
+----
+DEBUG ProducerCache - >>>> Endpoint[direct:start]
Exchange[Message: 01234567890123456789... [Body clipped after 20 chars, total
length is 1000]]
+----
+
+
+[tabs]
+====
+
+Java::
++
+In Java you can set the maximum length as a global option.
++
+[source,java]
+----
+context.getGlobalOptions().put(Exchange.LOG_DEBUG_BODY_MAX_CHARS, "500");
+----
+
+Application Properties::
++
+You can also set the limit in `application.properties`.
++
+[source,properties]
+-----
+camel.main.globalOptions[CamelLogDebugBodyMaxChars] = 500
+-----
+====
+
+NOTE: You can customize the limit when Camel clips the body in the log.
+You can use a limit of 0 to disable limit, so the entire body is
+shown. Setting a negative value, such as -1, means
+the message body is not logged at all.
+
+
== See Also
- xref:backlog-tracer.adoc[Backlog Tracer]
diff --git a/docs/user-manual/modules/faq/nav.adoc
b/docs/user-manual/modules/faq/nav.adoc
index b6f881f08449..d39c2d9c0eab 100644
--- a/docs/user-manual/modules/faq/nav.adoc
+++ b/docs/user-manual/modules/faq/nav.adoc
@@ -13,12 +13,7 @@
** xref:ROOT:languages.adoc[What languages are supported?]
** xref:what-platforms-are-supported.adoc[What platforms are supported?]
** xref:why-the-name-camel.adoc[Why the name Camel?]
-**
xref:how-do-i-specify-which-method-to-use-when-using-beans-in-routes.adoc[How
do I specify which method to use when using beans in routes?]
** xref:how-does-camel-look-up-beans-and-endpoints.adoc[How does Camel look up
beans and endpoints?]
-** xref:how-do-i-reuse-the-contexttestsupport-class-in-my-unit-tests.adoc[How
do I reuse the ContextTestSupport class in my unit tests?]
-**
xref:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[How
do I set the max chars when debug logging messages in Camel?]
-** xref:how-do-i-use-uris-with-parameters-in-xml.adoc[How do I use URIs with
parameters in XML?]
-**
xref:how-do-i-write-a-custom-processor-which-sends-multiple-messages.adoc[How
do I write a custom Processor which sends multiple messages?]
** xref:how-should-i-invoke-my-pojos-or-spring-services.adoc[How should I
invoke my POJOs or Spring Services?]
** xref:how-to-avoid-sending-some-or-all-message-headers.adoc[How to avoid
sending some or all message headers?]
** xref:how-to-remove-the-http-protocol-headers-in-the-camel-message.adoc[How
to remove the http protocol headers in the camel message?]
@@ -38,9 +33,6 @@
** xref:why-is-the-exception-null-when-i-use-onexception.adoc[Why is the
exception null when I use onException?]
** xref:why-use-multiple-camelcontext.adoc[Why use multiple CamelContext?]
** xref:how-do-i-use-log4j.adoc[How do I use log4j?]
-** xref:how-do-i-set-the-mep-when-interacting-with-jbi.adoc[How do I set the
MEP when interacting with JBI?]
-** xref:how-do-the-direct-event-seda-and-vm-endpoints-compare.adoc[How do the
direct, event, seda and vm endpoints compare?]
-** xref:how-do-the-timer-and-quartz-endpoints-compare.adoc[How do the Timer
and Quartz endpoints compare?]
** xref:why-does-my-jms-route-only-consume-one-message-at-once.adoc[Why does
my JMS route only consume one message at once?]
** xref:exception-orgapachecamelnosuchendpointexception.adoc[Exception -
org.apache.camel.NoSuchEndpointException]
** xref:exception-orgxmlsaxsaxparseexception.adoc[Exception -
org.xml.sax.SAXParseException]
diff --git
a/docs/user-manual/modules/faq/pages/how-do-i-reuse-the-contexttestsupport-class-in-my-unit-tests.adoc
b/docs/user-manual/modules/faq/pages/how-do-i-reuse-the-contexttestsupport-class-in-my-unit-tests.adoc
deleted file mode 100644
index 9c23c964405e..000000000000
---
a/docs/user-manual/modules/faq/pages/how-do-i-reuse-the-contexttestsupport-class-in-my-unit-tests.adoc
+++ /dev/null
@@ -1,7 +0,0 @@
-= How do I reuse the ContextTestSupport class in my unit tests?
-
-You might want to look at the various xref:ROOT:testing.adoc[Testing]
-to see if those are better,
-more powerful options. We see `ContextTestSupport` as an older, less
-powerful option.
-
diff --git
a/docs/user-manual/modules/faq/pages/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc
b/docs/user-manual/modules/faq/pages/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc
deleted file mode 100644
index 38d2e1a894e3..000000000000
---
a/docs/user-manual/modules/faq/pages/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc
+++ /dev/null
@@ -1,53 +0,0 @@
-= How do I set the max chars when debug logging messages in Camel?
-
-*Since Camel 2.0*
-
-When you run Camel with logging, it will log the messages and its
-content from time to time.
-As some messages can contain very big payloads Camel will by default
-clip the log message and only show the first 1000 chars.
-
-You will see this in the log as:
-
-----
-
-DEBUG ProducerCache - >>>> Endpoint[direct:start]
Exchange[Message: 01234567890123456789... [Body clipped after 20 chars, total
length is 1000]]
-----
-
-Here we have a big message that just contains many numbers. As its based
-on an unit test we have set a custom limit of 20 chars, and we have a
-payload with 1000 chars in total.
-
-You can customize the limit when Camel clips the body in the log.
-You can use a limit of 0 or negative to disable it so the entire body is
-shown.
-
-From *Camel 2.12* onwards, setting a negative value, such as -1, means
-the message body is not logged. For earlier Camel versions, you would
-need to set the value to 1, and have the first char logged.
-
-[[HowdoIsetthemaxcharswhendebugloggingmessagesinCamel-CustomizingfromJavaDSL]]
-== Customizing from Java DSL
-
-You add to the Camel properties the limit. For example to limit at 500
-chars:
-
-[source,java]
-----
- context.getGlobalOptions().put(Exchange.LOG_DEBUG_BODY_MAX_CHARS,
"500");
-----
-
-[[HowdoIsetthemaxcharswhendebugloggingmessagesinCamel-CustomizingfromSpringDSL]]
-== Customizing from Spring DSL
-
-You add to the Camel properties the limit. For example to limit at 500
-chars:
-
-[source,xml]
-----
- <camelContext>
- <properties>
- <property key="CamelLogDebugBodyMaxChars" value="500"/>
- </properties>
- </camelContext>
-----
diff --git
a/docs/user-manual/modules/faq/pages/how-do-i-set-the-mep-when-interacting-with-jbi.adoc
b/docs/user-manual/modules/faq/pages/how-do-i-set-the-mep-when-interacting-with-jbi.adoc
deleted file mode 100644
index c4b315ca16b2..000000000000
---
a/docs/user-manual/modules/faq/pages/how-do-i-set-the-mep-when-interacting-with-jbi.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-= How do I set the MEP when interacting with JBI?
-
-[[HowdoIsettheMEPwheninteractingwithJBI-Problem]]
-== Problem
-
-If you are using the Camel JBI integration to send a
-`MessageExchange` to another JBI component from within your Camel route,
-Camel uses the MEP of the underlying Camel Exchange to determine the MEP
-of the JBI `MessageExchange`. An example:
-
-[source,java]
-----
-from(""timer://foo").to("jbi:endpoint:urn:translator:endpoint").to("log:test");
//THIS WON'T WORK...
-----
-
-If the timer endpoint that starts the route sends a Camel exchange with
-an in-only MEP, the MEP for interacting with JBI will also be InOnly.
-Now imagine that the target JBI endpoint is in fact a
-http://servicemix.apache.org/servicemix-saxon.html[servicemix-saxon xslt
endpoint],
-that really expects an InOut MEP. This would break the Camel
-route above.
-
-[[HowdoIsettheMEPwheninteractingwithJBI-Solution]]
-== Solution
-
-For this case, you can override the MEP used from the Camel route
-like this, making sure that a JBI InOut `MessageExchange` is being used to
-interact with the `"urn:translation:endpoint"` endpoint.
-
-[source,java]
-----
-from("timer://foo").to("jbi:endpoint:urn:translator:endpoint?mep=in-out").to("log:test");
//...BUT THIS WILL
-----
diff --git
a/docs/user-manual/modules/faq/pages/how-do-i-specify-time-period-in-a-human-friendly-syntax.adoc
b/docs/user-manual/modules/faq/pages/how-do-i-specify-time-period-in-a-human-friendly-syntax.adoc
deleted file mode 100644
index 28025834f2ce..000000000000
---
a/docs/user-manual/modules/faq/pages/how-do-i-specify-time-period-in-a-human-friendly-syntax.adoc
+++ /dev/null
@@ -1,54 +0,0 @@
-= How do I specify time period in a human friendly syntax?
-
-*Since Camel 2.3*
-
-Some of the Camel xref:ROOT:component.adoc[components] offers options to
-specify a time period, which must be entered in milli second as unit.
-This may be unfriendly to read as a human when the value is large such
-as 45min = 2700000 millis.
-
-So in Camel 2.3 you can now configure any endpoint uri parameter using a
-String syntax, which at runtime will get converted to millis (`long`
-type).
-
-You can use the following short syntax, which is most common to use:
-
-[width="100%",cols="50%,50%",options="header",]
-|============
-|Syntax |Unit
-|h |hour
-|m |minute
-|s |second
-|============
-
-So for example the xref:components::timer-component.adoc[Timer] endpoint can
be configured as
-follows:
-
-[source,java]
-----
-from("timer:foo?period=45m").to("log:foo");
-----
-
-You can mix and match the units so you can do this as well:
-
-[source,java]
-----
-from("timer:foo?period=1h15m").to("log:foo");
-from("timer:bar?period=2h30s").to("log:bar");
-from("timer:bar?period=3h45m58s").to("log:bar");
-----
-
-However you can also use long syntax:
-
-[width="100%",cols="50%,50%",options="header",]
-|=========================
-|Syntax |Unit
-|hour or hours |hour
-|minute or minutes |minute
-|second or seconds |second
-|=========================
-
-[source,java]
-----
-from("timer:foo?period=45minutes").to("log:foo");
-----
diff --git
a/docs/user-manual/modules/faq/pages/how-do-i-specify-which-method-to-use-when-using-beans-in-routes.adoc
b/docs/user-manual/modules/faq/pages/how-do-i-specify-which-method-to-use-when-using-beans-in-routes.adoc
deleted file mode 100644
index cd8c283b543b..000000000000
---
a/docs/user-manual/modules/faq/pages/how-do-i-specify-which-method-to-use-when-using-beans-in-routes.adoc
+++ /dev/null
@@ -1,8 +0,0 @@
-= Ho do I specify which method to use when using beans in routes?
-
-See xref:components::bean-component.adoc[Bean],
xref:ROOT:bean-integration.adoc[Bean Integration]
-and xref:ROOT:bean-binding.adoc[Bean Binding]
-
-However if you have overloaded methods you need to specify which of
-those overloaded method you want to use by specifying parameter type
-qualifiers. See more details at xref:ROOT:bean-binding.adoc[Bean Binding].
diff --git
a/docs/user-manual/modules/faq/pages/how-do-i-use-uris-with-parameters-in-xml.adoc
b/docs/user-manual/modules/faq/pages/how-do-i-use-uris-with-parameters-in-xml.adoc
deleted file mode 100644
index 9d66c25c7fba..000000000000
---
a/docs/user-manual/modules/faq/pages/how-do-i-use-uris-with-parameters-in-xml.adoc
+++ /dev/null
@@ -1,50 +0,0 @@
-= How do I use URIs with parameters in XML?
-
-If you try and use one of the Camel xref:ROOT:uris.adoc[URIs] in an
-XML DSL using the URI query parameter notation, such as:
-
-[source,xml]
-----
-<route>
- <from uri="direct:start?paramA=1¶mB=2"/>
- <to uri="mock:result"/>
-</route>
-----
-
-you might get errors such as...
-
-----
-Caused by: org.xml.sax.SAXParseException: The reference to entity "paramB"
must end with the ';' delimiter.
- at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
- at
-----
-
-This is because in XML you need to escape some special XML characters
-like these:
-
-[width="100%",cols="50%,50%",options="header",]
-|==================================================
-|Special Character |How to escape it in XML
-a|`&`
-
-a|`+&+`
-
-a|`<`
-
-a|`+<+`
-
-a|`>`
-
-a|`+>+`
-
-|==================================================
-
-So if you write the following XML it should work...
-
-[source,xml]
-----
-<route>
- <from uri="direct:start?paramA=1&paramB=2"/>
- <to uri="mock:result"/>
-</route>
-----
diff --git
a/docs/user-manual/modules/faq/pages/how-do-i-write-a-custom-processor-which-sends-multiple-messages.adoc
b/docs/user-manual/modules/faq/pages/how-do-i-write-a-custom-processor-which-sends-multiple-messages.adoc
deleted file mode 100644
index 3c61ceb060b7..000000000000
---
a/docs/user-manual/modules/faq/pages/how-do-i-write-a-custom-processor-which-sends-multiple-messages.adoc
+++ /dev/null
@@ -1,50 +0,0 @@
-= How do I write a custom Processor which sends multiple messages?
-
-You could use a xref:components:eips:split-eip.adoc[Splitter] or use multiple
-xref:components:eips:message-translator.adoc[Message Translator] instances in
your
-route.
-
-Or you could write a custom processor which is injected with a
-`ProducerTemplate` instance that just generates N messages...
-
-[source,java]
-----
-public class MyProducer implements Processor {
- ProducerTemplate producer;
-
- public void setProducer(ProducerTemplate producer) {
- this.producer = producer;
- }
-
- public void process(Exchange inExchange) {
- // some loop for each message
- for (String template in templates) {
- // lets send a new exchange to the producers default destination
- // being called back so we can customize the message
- producer.send(new Processor() {
- public void process(Exchange outExchange) {
- outExchange.getIn().setBody("This is the body");
- // set some headers too?
- }
- });
- }
-}
-----
-
-Then the `ProducerTemplate` can be injected -- configured in `spring.xml`
-with its default URI:
-
-[source,xml]
-----
-<camelContext xmlns="http://camel.apache.org/schema/spring";>
- <template id="myTemplate" defaultEndpoint="activemq:someQueue"/>
-</camelContext>
-
-<bean id="foo" class="MyProducer">
- <property name="producer" ref="myTemplate"/>
-</bean>
-----
-
-Note that the default output URI is inherited from the `<template/>`
-configuration. If you prefer you could specify that in the
-`producer.send()` method call.
diff --git
a/docs/user-manual/modules/faq/pages/how-do-the-direct-event-seda-and-vm-endpoints-compare.adoc
b/docs/user-manual/modules/faq/pages/how-do-the-direct-event-seda-and-vm-endpoints-compare.adoc
deleted file mode 100644
index c7d799a67958..000000000000
---
a/docs/user-manual/modules/faq/pages/how-do-the-direct-event-seda-and-vm-endpoints-compare.adoc
+++ /dev/null
@@ -1,15 +0,0 @@
-= How do the `direct`, `event`, `seda`, and `vm` endpoints compare?
-
-* VM and xref:components::seda-component.adoc[SEDA] endpoints are basically the
-same; they both offer asychronous in memory SEDA queues; they differ in
-visibility -- endpoints are visible inside the same JVM or within the same
-CamelContext respectively.
-* xref:components::direct-component.adoc[Direct] uses no threading; it
directly invokes the
-consumer when sending.
-* xref:components::spring-event-component.adoc[Spring Event] adds a listener
to Spring's
-application events; so the consumer is invoked the same thread as Spring
-notifies events. Event differs in that the payload should be a Spring
-`ApplicationEvent` object whereas
xref:components::direct-component.adoc[Direct],
-xref:components::seda-component.adoc[SEDA] can use any payload.
-
-More information about when to use which component can be found in this
https://tomd.xyz/camel-direct-vm-seda/[guide].
diff --git
a/docs/user-manual/modules/faq/pages/how-do-the-timer-and-quartz-endpoints-compare.adoc
b/docs/user-manual/modules/faq/pages/how-do-the-timer-and-quartz-endpoints-compare.adoc
deleted file mode 100644
index 3ee7f106cbd4..000000000000
---
a/docs/user-manual/modules/faq/pages/how-do-the-timer-and-quartz-endpoints-compare.adoc
+++ /dev/null
@@ -1,7 +0,0 @@
-= How do the Timer and Quartz endpoints compare?
-
-xref:components::timer-component.adoc[Timer] is a simple, non persistence
timer using the
-JDK's in built timer mechanism.
-
-xref:components::quartz-component.adoc[Quartz] uses the Quartz library which
uses a database
-to store timer events and supports distributed timers and cron notation.
diff --git a/docs/user-manual/modules/faq/pages/index.adoc
b/docs/user-manual/modules/faq/pages/index.adoc
index a5e33f49feb7..34ce1fafece0 100644
--- a/docs/user-manual/modules/faq/pages/index.adoc
+++ b/docs/user-manual/modules/faq/pages/index.adoc
@@ -34,12 +34,7 @@ General questions about Camel
Questions on using Apache Camel
-*
xref:how-do-i-specify-which-method-to-use-when-using-beans-in-routes.adoc[How
do I specify which method to use when using beans in routes?]
* xref:how-does-camel-look-up-beans-and-endpoints.adoc[How does Camel look up
beans and endpoints?]
-* xref:how-do-i-reuse-the-contexttestsupport-class-in-my-unit-tests.adoc[How
do I reuse the ContextTestSupport class in my unit tests?]
-*
xref:how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[How
do I set the max chars when debug logging messages in Camel?]
-* xref:how-do-i-use-uris-with-parameters-in-xml.adoc[How do I use URIs with
parameters in XML?]
-*
xref:how-do-i-write-a-custom-processor-which-sends-multiple-messages.adoc[How
do I write a custom Processor which sends multiple messages?]
* xref:how-should-i-invoke-my-pojos-or-spring-services.adoc[How should I
invoke my POJOs or Spring Services?]
* xref:how-to-avoid-sending-some-or-all-message-headers.adoc[How to avoid
sending some or all message headers?]
* xref:how-to-create-executable-jar-camel-main.adoc[How to create executable
JAR for camel-main project?]
@@ -68,21 +63,6 @@ xref:components::log-component.adoc[Log] endpoint or JDK 1.4
logging or Log4j et
* xref:how-do-i-use-log4j.adoc[How do I use log4j?]
-[[FAQ-CamelEndpointQuestions]]
-== Camel Endpoint Questions
-
-Questions on using the various Camel xref:components::index.adoc[Components]
-and xref:ROOT:endpoint.adoc[Endpoint] implementations
-
-* xref:how-do-i-set-the-mep-when-interacting-with-jbi.adoc[How do I set the
MEP when interacting with JBI?]
-* xref:how-do-the-direct-event-seda-and-vm-endpoints-compare.adoc[How do the
direct, event, seda and vm endpoints compare?]
-* xref:how-do-the-timer-and-quartz-endpoints-compare.adoc[How do the Timer and
Quartz endpoints compare?]
-
-[[FAQ-ComponentQuestions]]
-== Component Questions
-
-Questions on using specific components
-
[[FAQ-JMSQuestions]]
=== JMS Questions
