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 eb45f008ff80 CAMEL-16861: Update FAQs
eb45f008ff80 is described below

commit eb45f008ff803719510c21bc2cd2648b65cb73e3
Author: Claus Ibsen <[email protected]>
AuthorDate: Wed Feb 25 20:44:29 2026 +0100

    CAMEL-16861: Update FAQs
---
 .../src/main/docs/cxf-component.adoc               |  16 ++
 docs/user-manual/modules/faq/nav.adoc              |   6 -
 .../exception-beandefinitionstoreexception.adoc    |  49 ------
 ...tion-orgapachecamelnosuchendpointexception.adoc |  10 +-
 .../exception-orgxmlsaxsaxparseexception.adoc      |  12 +-
 ...an-i-create-a-custom-component-or-endpoint.adoc |   3 +-
 ...on-ip-address-from-the-camel-cxf-consumer-.adoc |  16 --
 .../faq/pages/how-can-i-get-the-source-code.adoc   |   1 -
 .../pages/how-can-i-stop-a-route-from-a-route.adoc | 195 ---------------------
 ...ults-with-stacktraces-when-using-camel-cxf.adoc |   5 -
 .../faq/pages/how-do-i-become-a-committer.adoc     |  34 +---
 .../faq/pages/how-do-i-change-the-logging.adoc     |  19 --
 .../faq/pages/how-do-i-compile-the-code.adoc       |   3 -
 docs/user-manual/modules/faq/pages/index.adoc      |   6 -
 14 files changed, 36 insertions(+), 339 deletions(-)

diff --git 
a/components/camel-cxf/camel-cxf-soap/src/main/docs/cxf-component.adoc 
b/components/camel-cxf/camel-cxf-soap/src/main/docs/cxf-component.adoc
index 1a33d087de56..8864b969fc4b 100644
--- a/components/camel-cxf/camel-cxf-soap/src/main/docs/cxf-component.adoc
+++ b/components/camel-cxf/camel-cxf-soap/src/main/docs/cxf-component.adoc
@@ -1117,5 +1117,21 @@ public static class MyProcessor implements Processor {
 ----
 
 
+=== How can I get the remote connection IP address from the camel-cxf consumer 
?
+
+You can access the CXF Message by using the key of
+`CamelCxfMessage` from message header, and you can get the
+`ServletRequest` instance from the CXF message, then you can get the
+remote connection IP easily.
+
+Here is the code snippet:
+
+[source,java]
+----
+// check the remote IP from the CXF Message
+org.apache.cxf.message.Message cxfMessage = 
exchange.getIn().getHeader(CxfConstants.CAMEL_CXF_MESSAGE, 
org.apache.cxf.message.Message.class);
+ServletRequest request = (ServletRequest) cxfMessage.get("HTTP.REQUEST");
+String remoteAddress = request.getRemoteAddr();
+----
 
 include::spring-boot:partial$starter.adoc[]
diff --git a/docs/user-manual/modules/faq/nav.adoc 
b/docs/user-manual/modules/faq/nav.adoc
index 6e26ab50842c..bfcb5ed22913 100644
--- a/docs/user-manual/modules/faq/nav.adoc
+++ b/docs/user-manual/modules/faq/nav.adoc
@@ -5,7 +5,6 @@
 ** xref:how-does-camel-work.adoc[How does Camel work?]
 ** xref:how-does-the-website-work.adoc[How does the website work?]
 ** xref:how-do-i-become-a-committer.adoc[How do I become a committer?]
-** xref:how-do-i-compile-the-code.adoc[How do I compile the code?]
 ** xref:how-do-i-edit-the-website.adoc[How do I edit the website?]
 ** xref:running-camel-standalone.adoc[Running Camel standalone]
 ** xref:what-is-a-router.adoc[What is a router?]
@@ -16,11 +15,7 @@
 ** 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-can-i-create-a-custom-component-or-endpoint.adoc[How can I create 
a custom component or endpoint?]
-** 
xref:how-can-i-get-the-remote-connection-ip-address-from-the-camel-cxf-consumer-.adoc[How
 can I get the remote connection IP address from the camel-cxf consumer ?]
-** xref:how-can-i-stop-a-route-from-a-route.adoc[How can I stop a route from a 
route?]
-** 
xref:how-can-webservice-clients-see-remote-faults-with-stacktraces-when-using-camel-cxf.adoc[How
 can webservice clients see remote faults with stacktraces when using 
camel-cxf?]
 ** xref:how-does-camel-look-up-beans-and-endpoints.adoc[How does Camel look up 
beans and endpoints?]
-** xref:how-do-i-change-the-logging.adoc[How do I change the logging?]
 ** xref:how-do-i-configure-endpoints.adoc[How do I configure endpoints?]
 ** 
xref:how-do-i-configure-password-options-on-camel-endpoints-without-the-value-being-encoded.adoc[How
 do I configure password options on Camel endpoints without the value being 
encoded?]
 ** 
xref:how-do-i-configure-the-default-maximum-cache-size-for-producercache-or-producertemplate.adoc[How
 do I configure the default maximum cache size for ProducerCache or 
ProducerTemplate?]
@@ -66,7 +61,6 @@
 ** 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-beandefinitionstoreexception.adoc[Exception - 
BeanDefinitionStoreException]
 ** xref:exception-orgapachecamelnosuchendpointexception.adoc[Exception - 
org.apache.camel.NoSuchEndpointException]
 ** xref:exception-orgxmlsaxsaxparseexception.adoc[Exception - 
org.xml.sax.SAXParseException]
 ** xref:memory-leak-when-adding-and-removing-routes-at-runtime.adoc[Memory 
leak when adding and removing routes at runtime]
diff --git 
a/docs/user-manual/modules/faq/pages/exception-beandefinitionstoreexception.adoc
 
b/docs/user-manual/modules/faq/pages/exception-beandefinitionstoreexception.adoc
deleted file mode 100644
index d50d9388828f..000000000000
--- 
a/docs/user-manual/modules/faq/pages/exception-beandefinitionstoreexception.adoc
+++ /dev/null
@@ -1,49 +0,0 @@
-= BeanDefinitionStoreException
-
-If you use ActiveMQ 5.x that ships with Camel 1.x and you upgrade it to
-use Camel 2.0 you can get an exception while starting.
-
-----
-ERROR: java.lang.RuntimeException: Failed to execute start task. Reason:
-org.springframework.beans.factory.BeanDefinitionStoreException: Unrecognized
-xbean namespace mapping: http://activemq.apache.org/camel/schema/spring
-----
-
-The reason is basically that the XML namespace changed in Camel 2.0 as
-explained below.
-
-When Camel went from an ActiveMQ sub project to a top level apache
-project, they changed the URIs for their xml schemas to reflect this in
-Camel 2.0.
-
-To fix this, in `activemq.xml` change all occurrences of:
-
-[source,xml]
-----
-http://activemq.apache.org/camel/schema/spring
-----
-
-to
-
-[source,xml]
-----
-http://camel.apache.org/schema/spring
-----
-
-and
-
-[source,xml]
-----
-http://activemq.apache.org/camel/schema/spring/camel-spring.xsd
-----
-
-to
-
-[source,xml]
-----
-http://camel.apache.org/schema/spring/camel-spring.xsd
-----
-
-These will probably occur in the xsi:schemaLocation attribute of the top
-level beans tag (both) and in the xmlns attribute in the `camelContext`
-element (just the first).
diff --git 
a/docs/user-manual/modules/faq/pages/exception-orgapachecamelnosuchendpointexception.adoc
 
b/docs/user-manual/modules/faq/pages/exception-orgapachecamelnosuchendpointexception.adoc
index 68a095bcc2ba..487f046884eb 100644
--- 
a/docs/user-manual/modules/faq/pages/exception-orgapachecamelnosuchendpointexception.adoc
+++ 
b/docs/user-manual/modules/faq/pages/exception-orgapachecamelnosuchendpointexception.adoc
@@ -13,12 +13,12 @@ the classpath, you'll run into this exception:
 org.apache.camel.NoSuchEndpointException: No endpoint could be found for: 
jetty:http://localhost:8080/bus
 ----
 
+For example in a route such as XML:
+
 [source,xml]
 ----
-<camelContext id="camel" 
xmlns="http://activemq.apache.org/camel/schema/spring";>
-  <route>
+<route>
     <from uri="jetty:http://localhost:8080/bus"; />
-    <to uri="file://C:/tmp/something.xml" /> 
-  </route>
-</camelContext>
+    <to uri="file://C:/tmp/something.xml" />
+</route>
 ----
diff --git 
a/docs/user-manual/modules/faq/pages/exception-orgxmlsaxsaxparseexception.adoc 
b/docs/user-manual/modules/faq/pages/exception-orgxmlsaxsaxparseexception.adoc
index b917a595a9fb..b67733a8ab71 100644
--- 
a/docs/user-manual/modules/faq/pages/exception-orgxmlsaxsaxparseexception.adoc
+++ 
b/docs/user-manual/modules/faq/pages/exception-orgxmlsaxsaxparseexception.adoc
@@ -5,10 +5,10 @@ The reference to entity "..." must end with the ';' delimiter.
 ----
 
 In the URIs used for specifying Camel endpoints, the `&` is used to
-separate the parameters. However, `&` also is a reserved character in
-XML.
+separate the parameters. However, `&` also is a reserved character in XML.
+
 Because of this, you have to replace all & in your URIs by `+&amp;+` when
-using the Spring XML syntax to configure Camel routes.
+using the XML DSL to configure Camel routes.
 
 An example: this snippet of code in the xref:ROOT:dsl.adoc[DSL]...
 
@@ -17,9 +17,9 @@ An example: this snippet of code in the 
xref:ROOT:dsl.adoc[DSL]...
 from("timer://myTimer?fixedRate=true&delay=0&period=2000")
 ----
 
-...matches this example in the Spring XML syntax:
+... matches this example in the XML syntax where `&` has been replaced with 
`+&amp;+`
 
-[source,java]
+[source,xml]
 ----
-<from>timer://myTimer?fixedRate=true&amp;delay=0&amp;period=2000</from>
+<from uri="timer://myTimer?fixedRate=true&amp;delay=0&amp;period=2000"/>
 ----
diff --git 
a/docs/user-manual/modules/faq/pages/how-can-i-create-a-custom-component-or-endpoint.adoc
 
b/docs/user-manual/modules/faq/pages/how-can-i-create-a-custom-component-or-endpoint.adoc
index 58abf1f7dbe6..842db5c355d3 100644
--- 
a/docs/user-manual/modules/faq/pages/how-can-i-create-a-custom-component-or-endpoint.adoc
+++ 
b/docs/user-manual/modules/faq/pages/how-can-i-create-a-custom-component-or-endpoint.adoc
@@ -1,6 +1,5 @@
 = How can I create a custom component or endpoint?
 
 Please read xref:ROOT:writing-components.adoc[Writing Components] for a
-background in how to implement a new component or endpoint. Its really
-easy to do! :smile:
+background in how to implement a new component or endpoint.
 
diff --git 
a/docs/user-manual/modules/faq/pages/how-can-i-get-the-remote-connection-ip-address-from-the-camel-cxf-consumer-.adoc
 
b/docs/user-manual/modules/faq/pages/how-can-i-get-the-remote-connection-ip-address-from-the-camel-cxf-consumer-.adoc
deleted file mode 100644
index c39418ba2710..000000000000
--- 
a/docs/user-manual/modules/faq/pages/how-can-i-get-the-remote-connection-ip-address-from-the-camel-cxf-consumer-.adoc
+++ /dev/null
@@ -1,16 +0,0 @@
-= How can I get the remote connection IP address from the camel-cxf consumer ?
-
-From *Camel 2.6.0*, you can access the CXF Message by using the key of
-`CamelCxfMessage` from message header, and you can get the
-`ServletRequest` instance from the CXF message, then you can get the
-remote connection IP easily.
-
-Here is the code snippet:
-
-[source,java]
-----
-// check the remote IP from the CXF Message
-org.apache.cxf.message.Message cxfMessage = 
exchange.getIn().getHeader(CxfConstants.CAMEL_CXF_MESSAGE, 
org.apache.cxf.message.Message.class);
-ServletRequest request = (ServletRequest) cxfMessage.get("HTTP.REQUEST");
-String remoteAddress = request.getRemoteAddr();
-----
diff --git 
a/docs/user-manual/modules/faq/pages/how-can-i-get-the-source-code.adoc 
b/docs/user-manual/modules/faq/pages/how-can-i-get-the-source-code.adoc
index 39fab3e5370b..9a90b095b688 100644
--- a/docs/user-manual/modules/faq/pages/how-can-i-get-the-source-code.adoc
+++ b/docs/user-manual/modules/faq/pages/how-can-i-get-the-source-code.adoc
@@ -7,7 +7,6 @@ to the project using the standard GitHub way.
 
 https://github.com/apache/camel/
 
-[[HowcanIgetthesourcecode-Buildingthecode]]
 == Building the code
 
 To then build the code see xref:ROOT:building.adoc[Building].
diff --git 
a/docs/user-manual/modules/faq/pages/how-can-i-stop-a-route-from-a-route.adoc 
b/docs/user-manual/modules/faq/pages/how-can-i-stop-a-route-from-a-route.adoc
deleted file mode 100644
index 5e62d2beb458..000000000000
--- 
a/docs/user-manual/modules/faq/pages/how-can-i-stop-a-route-from-a-route.adoc
+++ /dev/null
@@ -1,195 +0,0 @@
-= How can I stop a route from a route
-
-The xref:ROOT:camelcontext.adoc[CamelContext] provides API for managing
-routes at runtime. It has a `stopRoute(id)` and `startRoute(id)`
-methods.
-
-Stopping a route during routing an existing message is a bit tricky. The
-reason for that is Camel will xref:ROOT:graceful-shutdown.adoc[Graceful
-Shutdown] the route you are stopping. And if you do that while a message
-is being routed the xref:ROOT:graceful-shutdown.adoc[Graceful Shutdown] will
-try to wait until that message has been processed.
-
-The best practice for stopping a route from a route, is to either:
-
-* signal to another thread to stop the route
-* spin off a new thread to stop the route
-
-Using another thread to stop the route is also what is normally used
-when stopping Camel itself, or for example when an application in a
-server is stopped etc. Its too tricky and hard to stop a route using the
-same thread that currently is processing a message from the route. This
-is not advised to do, and can cause unforeseen side effects.
-
-[[HowcanIstoparoutefromaroute-UsingalatchtostopCamelfromaroute]]
-== Using a latch to stop Camel from a route
-
-In this example we use a `CountdownLatch` to signal when Camel should
-stop, triggered from a route.
-
-[source,java]
-----
-// use a latch as signal when to stop Camel
-private final CountDownLatch latch = new CountDownLatch(1);
-
-public void testStopCamelFromRoute() throws Exception {
-    // create camel, add routes, and start camel
-    CamelContext context = new DefaultCamelContext();
-    context.addRoutes(createMyRoutes());
-    context.start();
-
-    // setup mock expectations for unit test
-    MockEndpoint start = context.getEndpoint("mock:start", MockEndpoint.class);
-    start.expectedMessageCount(1);
-    MockEndpoint done = context.getEndpoint("mock:done", MockEndpoint.class);
-    done.expectedMessageCount(1);
-
-    // send a message to the route
-    ProducerTemplate template = context.createProducerTemplate();
-    template.sendBody("direct:start", "Hello Camel");
-
-    // wait for the latch (use 1 minute as fail safe, due unit test)
-    assertTrue(latch.await(1, TimeUnit.MINUTES));
-
-    // stop camel
-    context.stop();
-
-    // unit test assertions
-    start.assertIsSatisfied();
-    done.assertIsSatisfied();
-}
-----
-
-And in the route we call the latch as shown:
-
-[source,java]
-----
-public RouteBuilder createMyRoutes() throws Exception {
-    return new RouteBuilder() {
-        @Override
-        public void configure() throws Exception {
-            from("direct:start").routeId("myRoute")
-                .to("mock:start")
-                .process(new Processor() {
-                    @Override
-                    public void process(Exchange exchange) throws Exception {
-                        // stop Camel by signalling to the latch
-                        latch.countDown();
-                    }
-                }).to("mock:done");
-        }
-    };
-}
-----
-
-[[HowcanIstoparoutefromaroute-Usingathreadtostoparoutefromaroute]]
-== Using a thread to stop a route from a route
-
-In this example we use a separate `Thread` to stop the route, triggered
-from the route itself.
-
-[source,java]
-----
-public void testStopRouteFromRoute() throws Exception {
-    // create camel, add routes, and start camel
-    CamelContext context = new DefaultCamelContext();
-    context.addRoutes(createMyRoutes());
-    context.start();
-
-    assertTrue("Route myRoute should be started", 
context.getRouteStatus("myRoute").isStarted());
-    assertTrue("Route bar should be started", 
context.getRouteStatus("bar").isStarted());
-
-    // setup mock expectations for unit test
-    MockEndpoint start = context.getEndpoint("mock:start", MockEndpoint.class);
-    start.expectedMessageCount(1);
-    MockEndpoint done = context.getEndpoint("mock:done", MockEndpoint.class);
-    done.expectedMessageCount(1);
-
-    // send a message to the route
-    ProducerTemplate template = context.createProducerTemplate();
-    template.sendBody("direct:start", "Hello Camel");
-
-    // just wait a bit for the thread to stop the route
-    Thread.sleep(1000);
-
-    // the route should now be stopped
-    assertTrue("Route myRoute should be stopped", 
context.getRouteStatus("myRoute").isStopped());
-    assertTrue("Route bar should be started", 
context.getRouteStatus("bar").isStarted());
-
-    // stop camel
-    context.stop();
-
-    // unit test assertions
-    start.assertIsSatisfied();
-    done.assertIsSatisfied();
-}
-----
-
-And in the route we create the thread and call the `stopRoute` method as
-shown:
-
-[source,java]
-----
-public RouteBuilder createMyRoutes() throws Exception {
-    return new RouteBuilder() {
-        @Override
-        public void configure() throws Exception {
-            from("direct:start").routeId("myRoute")
-                .to("mock:start")
-                .process(new Processor() {
-                    Thread stop;
-
-                    @Override
-                    public void process(final Exchange exchange) throws 
Exception {
-                        // stop this route using a thread that will stop
-                        // this route gracefully while we are still running
-                        if (stop == null) {
-                            stop = new Thread() {
-                                @Override
-                                public void run() {
-                                    try {
-                                        
exchange.getContext().getRouteController().stopRoute("myRoute");
-                                    } catch (Exception e) {
-                                        // ignore
-                                    }
-                                }
-                            };
-                        }
-
-                        // start the thread that stops this route
-                        stop.start();
-                    }
-                }).to("mock:done");
-            
-            from("direct:bar").routeId("bar")
-                .to("mock:bar");
-        }
-    };
-}
-----
-
-[[HowcanIstoparoutefromaroute-Alternativesolutions]]
-== Alternative solutions
-
-Camel provides another feature for managing routes at runtime which is
-xref:ROOT:route-policy.adoc[RoutePolicy].
-
-And xref:ROOT:camelcontext.adoc[CamelContext] also provides API for
-suspend/resume of routes, and shutdown as well.
-
-* suspend/resume is faster than stop/start. For example a HTTP server
-will still run but deny any incoming requests.
-Whereas if it was stopped the HTTP listener would have been stopped.
-* shutdown means the route is being removed from
-xref:ROOT:camelcontext.adoc[CamelContext] and cannot be started again. Its
-also removed from JMX.
-A route must have been stopped prior to be shutdown.
-
-See more details about the xref:ROOT:lifecycle.adoc[Lifecycle].
-
-[NOTE]
-====
-You can also use the xref:components::controlbus-component.adoc[ControlBus] 
component to let
-it stop/start routes.
-====
-
diff --git 
a/docs/user-manual/modules/faq/pages/how-can-webservice-clients-see-remote-faults-with-stacktraces-when-using-camel-cxf.adoc
 
b/docs/user-manual/modules/faq/pages/how-can-webservice-clients-see-remote-faults-with-stacktraces-when-using-camel-cxf.adoc
deleted file mode 100644
index 511d3a9d2dcd..000000000000
--- 
a/docs/user-manual/modules/faq/pages/how-can-webservice-clients-see-remote-faults-with-stacktraces-when-using-camel-cxf.adoc
+++ /dev/null
@@ -1,5 +0,0 @@
-= How can webservice clients see remote faults with stacktraces when using 
camel-cxf?
-
-See Apache CXF documentation about
-http://cxf.apache.org/docs/debugging-and-logging.html#DebuggingandLogging-SOAPFaultfordebugging[SOAP
-fault for debugging].
diff --git 
a/docs/user-manual/modules/faq/pages/how-do-i-become-a-committer.adoc 
b/docs/user-manual/modules/faq/pages/how-do-i-become-a-committer.adoc
index 28708bd1f184..ae89fa98b448 100644
--- a/docs/user-manual/modules/faq/pages/how-do-i-become-a-committer.adoc
+++ b/docs/user-manual/modules/faq/pages/how-do-i-become-a-committer.adoc
@@ -14,23 +14,13 @@ patches; its also about helping out on the development and 
user
 link:/community/mailing-list/[Discussion Forums],
 helping with documentation and the issue tracker.
 
-[[HowdoIbecomeacommitter-Becomingacommittersteps]]
+When you have done that for a while, then someone from the Camel PMC team
+will invite you via email.
+
 == Becoming a committer steps
 
-* Download and print the Apache Contributor License Agreement from
-http://www.apache.org/dev/new-committers-guide.html[here]. You need to
-sign it and fax it to Apache. In the past I've found its often faster to
-also post it via snail mail :smile:
-* wait for your name to appear on the list of
-http://people.apache.org/~jim/committers.html#unlistedclas[received
-CLAs]
-* once thats done let us know and we can apply to Apache Infrastructure
-to have your account created; we'll also need to know
-** your full name
-** your preferred email address
-** your preferred unix account name
-
-[[HowdoIbecomeacommitter-GettingstartedatApache]]
+You will be invited, and the email have instructions how to proceed.
+
 == Getting started at Apache
 
 Firstly add yourself to the link:/community/team/[Team] page
@@ -39,22 +29,14 @@ Now go read the instructions on the
 http://www.apache.org/dev/new-committers-guide.html[new committers guide].
 Its also worth viewing http://www.apache.org/dev.
 
-[[HowdoIbecomeacommitter-Moreinformation]]
 == More information
 
 You can find more information about being a
 http://www.apache.org/dev/committers.html[committer at Apache here].
 
-[[HowdoIbecomeacommitter-GettingKarmainJIRAandConfluence]]
-== Getting Karma in JIRA and Confluence
+== Getting Karma in JIRA and GitHub
 
-Mail the dev list and ask for karma for JIRA / Confluence giving them
+Mail the dev list and ask for karma for JIRA / GitHub giving them
 details of your username you used to register with them both. We can
-then grant the necessary karma so you can start grabbing JIRA issues or
-editing the wiki
-
-[[HowdoIbecomeacommitter-GettingKarmainJenkinsHudson]]
-== Getting Karma in Jenkins / Hudson
+then grant the necessary karma so you can start grabbing JIRA issues.
 
-Mail the PMC chair and ask for karma for Jenkins / Hudson as described
-http://wiki.apache.org/general/Hudson[here].
diff --git 
a/docs/user-manual/modules/faq/pages/how-do-i-change-the-logging.adoc 
b/docs/user-manual/modules/faq/pages/how-do-i-change-the-logging.adoc
deleted file mode 100644
index b1f950793f2e..000000000000
--- a/docs/user-manual/modules/faq/pages/how-do-i-change-the-logging.adoc
+++ /dev/null
@@ -1,19 +0,0 @@
-= How do I change the logging?
-
-We use https://commons.apache.org/proper/commons-logging/[commons-logging] to
-log information in the broker client and the broker itself so you can
-fully configure the logging levels desired, whether to log to files or
-the console, as well as the underlying logging implementation (Log4J,
-Java SE logger, etc.) you wish to use. For Log4J, full instructions are
-in its https://logging.apache.org/log4j/2.x/manual/index.html[manual], but in
-a nutshell:
-
-* Add `log4j.jar` to your classpath
-* Create a `log4j.properties` file specifying desired logging
-configuration (The Camel distribution has example `log4j.properties` files
-you can use -- see for example in the
-https://github.com/apache/camel-examples/blob/main/examples/as2/src/main/resources/log4j.properties[/examples/camel-example-as2/src/main/resources]
 folder.)
-* Place the `log4j.properties` file in the folder where the compiled
-`.class` files are located (typically the `classes` folder) -- this will
-place the properties file on the classpath, where it needs to be at
-runtime.
diff --git a/docs/user-manual/modules/faq/pages/how-do-i-compile-the-code.adoc 
b/docs/user-manual/modules/faq/pages/how-do-i-compile-the-code.adoc
deleted file mode 100644
index df1aa43517d1..000000000000
--- a/docs/user-manual/modules/faq/pages/how-do-i-compile-the-code.adoc
+++ /dev/null
@@ -1,3 +0,0 @@
-= How do I compile from the source code?
-
-See the xref:ROOT:building.adoc[Building] page.
diff --git a/docs/user-manual/modules/faq/pages/index.adoc 
b/docs/user-manual/modules/faq/pages/index.adoc
index da244fa29504..60ee1559dcdc 100644
--- a/docs/user-manual/modules/faq/pages/index.adoc
+++ b/docs/user-manual/modules/faq/pages/index.adoc
@@ -20,7 +20,6 @@ General questions about Camel
 * xref:how-does-camel-work.adoc[How does Camel work?]
 * xref:how-does-the-website-work.adoc[How does the website work?]
 * xref:how-do-i-become-a-committer.adoc[How do I become a committer?]
-* xref:how-do-i-compile-the-code.adoc[How do I compile the code?]
 * xref:how-do-i-edit-the-website.adoc[How do I edit the website?]
 * xref:running-camel-standalone.adoc[Running Camel standalone]
 * xref:what-is-a-router.adoc[What is a router?]
@@ -37,11 +36,7 @@ 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-can-i-create-a-custom-component-or-endpoint.adoc[How can I create a 
custom component or endpoint?]
-* 
xref:how-can-i-get-the-remote-connection-ip-address-from-the-camel-cxf-consumer-.adoc[How
 can I get the remote connection IP address from the camel-cxf consumer ?]
-* xref:how-can-i-stop-a-route-from-a-route.adoc[How can I stop a route from a 
route?]
-* 
xref:how-can-webservice-clients-see-remote-faults-with-stacktraces-when-using-camel-cxf.adoc[How
 can webservice clients see remote faults with stacktraces when using 
camel-cxf?]
 * xref:how-does-camel-look-up-beans-and-endpoints.adoc[How does Camel look up 
beans and endpoints?]
-* xref:how-do-i-change-the-logging.adoc[How do I change the logging?]
 * xref:how-do-i-configure-endpoints.adoc[How do I configure endpoints?]
 * 
xref:how-do-i-configure-password-options-on-camel-endpoints-without-the-value-being-encoded.adoc[How
 do I configure password options on Camel endpoints without the value being 
encoded?]
 * 
xref:how-do-i-configure-the-default-maximum-cache-size-for-producercache-or-producertemplate.adoc[How
 do I configure the default maximum cache size for ProducerCache or 
ProducerTemplate?]
@@ -119,7 +114,6 @@ Questions on using the 
xref:components::jms-component.adoc[JMS] endpoints in Cam
 
 Common Problems that people have when riding the Camel
 
-* xref:exception-beandefinitionstoreexception.adoc[Exception - 
BeanDefinitionStoreException]
 * xref:exception-orgapachecamelnosuchendpointexception.adoc[Exception - 
org.apache.camel.NoSuchEndpointException]
 * xref:exception-orgxmlsaxsaxparseexception.adoc[Exception - 
org.xml.sax.SAXParseException]
 * xref:memory-leak-when-adding-and-removing-routes-at-runtime.adoc[Memory leak 
when adding and removing routes at runtime]

Reply via email to