This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch faq in repository https://gitbox.apache.org/repos/asf/camel.git
commit 64dabba8be4aff8f9e820367ba5cb557ea1fb020 Author: Claus Ibsen <[email protected]> AuthorDate: Tue Mar 3 19:38:21 2026 +0100 CAMEL-16861: Cleanup docs --- .../camel-spring/src/main/docs/spring-summary.adoc | 3 - docs/user-manual/modules/ROOT/pages/component.adoc | 2 +- docs/user-manual/modules/ROOT/pages/endpoint.adoc | 262 +++++++++++++++++- docs/user-manual/modules/ROOT/pages/index.adoc | 1 - docs/user-manual/modules/ROOT/pages/uris.adoc | 2 +- docs/user-manual/modules/faq/nav.adoc | 2 - .../faq/pages/how-can-i-get-the-source-code.adoc | 9 +- .../faq/pages/how-do-i-configure-endpoints.adoc | 305 --------------------- ...-endpoints-without-the-value-being-encoded.adoc | 11 - docs/user-manual/modules/faq/pages/index.adoc | 2 - .../pages/why-cant-i-use-sign-in-my-password.adoc | 4 - 11 files changed, 267 insertions(+), 336 deletions(-) diff --git a/components/camel-spring-parent/camel-spring/src/main/docs/spring-summary.adoc b/components/camel-spring-parent/camel-spring/src/main/docs/spring-summary.adoc index aa7c86f90664..9b4a9d251b0f 100644 --- a/components/camel-spring-parent/camel-spring/src/main/docs/spring-summary.adoc +++ b/components/camel-spring-parent/camel-spring/src/main/docs/spring-summary.adoc @@ -398,9 +398,6 @@ the above example), then you can refer to the component using SpringCamelContext lazily fetching components from the spring context for the scheme name you use for Endpoint URIs. -For more details, see xref:manual:faq:how-do-i-configure-endpoints.adoc[Configuring -Endpoints and Components]. - == CamelContextAware If you want the `CamelContext` to be injected diff --git a/docs/user-manual/modules/ROOT/pages/component.adoc b/docs/user-manual/modules/ROOT/pages/component.adoc index a29642e31df3..81f2f7dc1f54 100644 --- a/docs/user-manual/modules/ROOT/pages/component.adoc +++ b/docs/user-manual/modules/ROOT/pages/component.adoc @@ -124,7 +124,7 @@ Camel identifies the components in the above example as `pop3`, `jms`, `urn`, an [NOTE] ==== -Make sure to read xref:faq:how-do-i-configure-endpoints.adoc[How do I configure endpoints?] +Make sure to read xref:endpoint.adoc[Endpoint] to learn more about configuring endpoints. For example, how to refer to beans in the xref:registry.adoc[Registry] or how to use raw values for password options, and using xref:using-propertyplaceholder.adoc[property placeholders] etc. ==== diff --git a/docs/user-manual/modules/ROOT/pages/endpoint.adoc b/docs/user-manual/modules/ROOT/pages/endpoint.adoc index 704a7bb9bc9f..f5ba03c9dfc7 100644 --- a/docs/user-manual/modules/ROOT/pages/endpoint.adoc +++ b/docs/user-manual/modules/ROOT/pages/endpoint.adoc @@ -47,7 +47,267 @@ YAML:: ---- ==== -== Endpoint API +=== Referring beans from endpoints + +When configuring endpoints using the URI syntax you can refer to beans +in the xref:registry.adoc[Registry] using the `#bean:id` notation. + +NOTE: The older syntax with just `#id` has been deprecated due to ambiguity +as Camel supports a number of additional functions that start with the # notation. + +If the URI parameter value starts with `#bean:` then Camel will lookup in +the xref:registry.adoc[Registry] for a bean of the given type by id. For instance: + +[tabs] +==== + +Java:: ++ +[source,java] +---- +from("file:messages/foo?sorter=#bean:mySpecialFileSorter") + .to("jms:queue:foo"); +---- + +XML:: ++ +[source,xml] +---- +<route> + <from uri="file:messages/foo?sorter=#bean:mySpecialFileSorter"/> + <to uri="jms:queue:foo"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: file:messages/foo?sorter=#bean:mySpecialFileSorter + steps: + - to: + uri: jms:queue:foo +---- +==== + +Will lookup a bean with the id `mySpecialFileSorter` in the Registry. + +==== Referring beans by class + +Camel also supports to refer to beans by their class type, such as `#class:com.foo.MySpecialSorter`, +which then will create a new bean instance of the given class name. + +If you need to provide parameters to the constructor, then this is also possible +(limited to numbers, boolean, literal, and null values) + +[source,text] +---- +file://inbox?sorter=#class:com.foo.MySpecialSorter(10, 'Hello world', true) +---- + +TIP: Inlining constructor arguments is only recommended for beans with a few options so the code is easy to understand and maintain. +Also beware that if the bean constructor is refactored then the string text would need to be updated accordingly. + +==== Referring beans by type + +When configuring endpoints using URI syntax you can now refer to bean by its type which +are used to lookup the bean by the given type from the xref:ROOT:registry.adoc[Registry]. + +If there is one bean found in the registry of the given type, then that bean instance will be used; +otherwise an exception is thrown. + +For example below we expect there is a single bean of the `org.apache.camel.spi.IdempotentRepository` type +in the xref:registry.adoc[Registry] that the file endpoint should use. + +[source,text] +---- +file://inbox?idempontentRepository=#type:org.apache.camel.spi.IdempotentRepository +---- + +=== Configuring parameter values using raw values, such as passwords + +When configuring endpoint options using URI syntax, then the values is +by default URI encoded. This can be a problem if you want to configure +passwords and just use the value _as is_ without any encoding. For +example, you may have a plus sign in the password, which would be decimal +encoded by default. + +You can define parameter value to be *raw* using the following syntax `RAW(value)`, e.g. +the value starts with `RAW(` and then ends with the parenthesis `)`. + +Here is a little example with the password: `se+re?t&23`: + +[tabs] +==== + +Java:: ++ +[source,java] +---- +from("file:inbox") + .to("ftp:[email protected]?password=RAW(se+re?t&23)&binary=true"); +---- + +XML:: ++ +[source,xml] +---- +<route> + <from uri="file:inbox"/> + <to uri="ftp:[email protected]?password=RAW(se+re?t&23)&binary=true"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: file:inbox + steps: + - to: + uri: ftp:[email protected]?password=RAW(se+re?t&23)&binary=true +---- + +YAML expanded:: ++ +[source,yaml] +---- +- route: + from: + uri: file + parameters: + directoryName: inbox + steps: + - to: + uri: ftp + parameters: + host: [email protected] + password: "RAW(se+re?t&23)" + binary: true +---- +==== + +In the above example, we have declared the password value as raw, and the +actual password would be as typed, eg `se+re?t&23`. + +NOTE: you may find a corner case when you use both `)` and `&` character as part of your password (ie, `se+re)t&23`). The parser will interpret the `)` as closing the `RAW` function and having a parameter started by `&`. In such case, you can instead use the `RAW{}` notation to let you include the `)` character and have it decoded as part of the password (ie, `RAW{se+re)t&23}`). As a safe alternative you can also use `password=#property:myPass` and then have `myPass` a xref:ROOT:property [...] + +==== Using ENV variables with raw values + +If you need to use environment variables, for example as username or passwords then this is now possible by inlining +the xref:components:languages:simple-language.adoc[Simple] language +using `+++$simple{xxx}+++` syntax in `RAW(...)` as shown below: + +[tabs] +==== + +Java:: ++ +[source,java] +---- +from("file:inbox") + .to("ftp:[email protected]?password=RAW($simple{env:MY_FTP_PASSWORD})&binary=true"); +---- + +XML:: ++ +[source,xml] +---- +<route> + <from uri="file:inbox"/> + <to uri="ftp:[email protected]?password=RAW($simple{env:MY_FTP_PASSWORD})&binary=true"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: file:inbox + steps: + - to: + uri: "ftp:[email protected]?password=RAW($simple{env:MY_FTP_PASSWORD})&binary=true" +---- + +==== + +=== Endpoint URIs with property placeholders + +Camel has extensive support for using xref:using-propertyplaceholder.adoc[]. + +For example in the ftp example above we can externalize the password to the `application.properties` file. + +[source,properties] +---- +myFtpPassword=RAW(se+re?t&23) +---- + +And the Camel routes can then refer to this placeholder using `{\{key}}` style. + +[tabs] +==== + +Java:: ++ +[source,java] +---- +from("file:inbox") + .to("ftp:[email protected]?password={{myFtpPassword}}&binary=true"); +---- + +XML:: ++ +[source,xml] +---- +<route> + <from uri="file:inbox"/> + <to uri="ftp:[email protected]?password={{myFtpPassword}}&binary=true"/> +</route> +---- + +YAML:: ++ +[source,yaml] +---- +- route: + from: + uri: file:inbox + steps: + - to: + uri: "ftp:[email protected]?password={{myFtpPassword}}&binary=true" +---- +==== + +And have a `application.properties` file with password. Notice we still define +the `RAW(value)` style to ensure the password is used _as is_: + +[source,properties] +---- +myFtpPassword=RAW(se+re?t&23) +---- + +We could still have used the `RAW(value)` in the Camel route instead: + +[source,java] +---- +.to("ftp:[email protected]?password=RAW({{myFtpPassword}})&binary=true") +---- + +And then we would need to remove the `RAW` from the properties file: + +[source,properties] +---- +myFtpPassword=se+re?t&23 +---- + + +== Java Endpoint API You will almost never have the need for creating endpoints manually via Java API. diff --git a/docs/user-manual/modules/ROOT/pages/index.adoc b/docs/user-manual/modules/ROOT/pages/index.adoc index ecee94f6b679..2a2403e425dc 100644 --- a/docs/user-manual/modules/ROOT/pages/index.adoc +++ b/docs/user-manual/modules/ROOT/pages/index.adoc @@ -46,7 +46,6 @@ For a deeper and better understanding of Apache Camel, an xref:faq:what-is-camel * xref:getting-started.adoc[Getting Started] * xref:book-getting-started.adoc[Longer Getting Started Guide] * xref:spring.adoc[Working with Camel and Spring] -* xref:faq:how-do-i-configure-endpoints.adoc[How do I configure endpoints?] * xref:camelcontext-autoconfigure.adoc[Auto Configuration] * xref:bean-integration.adoc[Bean Integration] * xref:configuring-route-startup-ordering-and-autostartup.adoc[Configuring route startup ordering and autostartup] diff --git a/docs/user-manual/modules/ROOT/pages/uris.adoc b/docs/user-manual/modules/ROOT/pages/uris.adoc index 58df63d9349d..d5618e05e9ed 100644 --- a/docs/user-manual/modules/ROOT/pages/uris.adoc +++ b/docs/user-manual/modules/ROOT/pages/uris.adoc @@ -20,4 +20,4 @@ The query parameters have two parameters: == More Information -You can read the guide xref:faq:how-do-i-configure-endpoints.adoc[How do I configure endpoints] to learn more about configuring _endpoints_. Among other things, this guide explains how to refer to beans in the xref:registry.adoc[registry], how to use raw values for password options, how to use xref:using-propertyplaceholder.adoc[property placeholders], or how to use the type safe xref:Endpoint-dsl.adoc[Endpoint DSL] and xref:dataformat-dsl.adoc[DataFormat DSL]. +See also xref:endpoint.adoc[] diff --git a/docs/user-manual/modules/faq/nav.adoc b/docs/user-manual/modules/faq/nav.adoc index bfcb5ed22913..767a840ce965 100644 --- a/docs/user-manual/modules/faq/nav.adoc +++ b/docs/user-manual/modules/faq/nav.adoc @@ -16,8 +16,6 @@ ** 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-does-camel-look-up-beans-and-endpoints.adoc[How does Camel look up beans and endpoints?] -** 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?] ** xref:how-do-i-configure-the-maximum-endpoint-cache-size-for-camelcontext.adoc[How do I configure the maximum endpoint cache size for CamelContext?] ** xref:how-do-i-debug-my-route.adoc[How do I debug my route?] 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 9a90b095b688..64ec91bebead 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 @@ -1,11 +1,10 @@ = How can I get the source code? -The source code is at https://github.com/apache/camel/ -so you can also checkout the source code from GitHub, if you are -familiar with using GitHub. By using GitHub you can submit pull requests -to the project using the standard GitHub way. +The source code is on GitHub at: https://github.com/apache/camel -https://github.com/apache/camel/ +From GitHub you can checkout the code, and contribute back +by sending Pull Requests. Working with the code is similar to +other projects hosted on GitHub. == Building the code diff --git a/docs/user-manual/modules/faq/pages/how-do-i-configure-endpoints.adoc b/docs/user-manual/modules/faq/pages/how-do-i-configure-endpoints.adoc deleted file mode 100644 index 79ec4d547a09..000000000000 --- a/docs/user-manual/modules/faq/pages/how-do-i-configure-endpoints.adoc +++ /dev/null @@ -1,305 +0,0 @@ -= How do I configure endpoints? - -There are a few different approaches to configuring components and -endpoints. - -[[HowdoIconfigureendpoints-UsingJavaCode]] -== Using Java Code - -You can explicitly configure a Component using Java -code as shown in this example - -Or you can explicitly get hold of an Endpoint and -configure it using Java code as shown in the xref:components::mock-component.adoc[Mock endpoint examples]. - -[source,java] ----- -SomeEndpoint endpoint = camelContext.getEndpoint("someURI", SomeEndpoint.class); -endpoint.setSomething("aValue"); ----- - -[[HowdoIconfigureendpoints-UsingSpringXML]] -== Using Spring XML - -You can configure your Component or Endpoint instances in your Spring XML as `<bean>` as follows: - -[source,xml] ----- -<bean id="activemq" class="org.apache.activemq.camel.component.ActiveMQComponent"> - <property name="connectionFactory"> - <bean class="org.apache.activemq.ActiveMQConnectionFactory"> - <property name="brokerURL" value="vm://localhost?broker.persistent=false&broker.useJmx=false"/> - </bean> - </property> -</bean> ----- - -Which allows you to configure a component using some name (activemq in -the above example), then you can refer to the component using -`activemq:[queue:|topic:]destinationName`. This works by the -`SpringCamelContext` lazily fetching components from the spring context -for the scheme name you use for Endpoint -URIs - -[[HowdoIconfigureendpoints-UsingEndpointURIs]] -== Using Endpoint URIs - -Another approach is to use the URI syntax. The URI syntax supports the -query notation. So for example with the xref:components::mail-component.adoc[Mail] component -you can configure the password property via the URI - -[source,text] ----- -pop3://host:port?password=foo ----- - -[[HowdoIconfigureendpoints-ReferringbeansfromEndpointURIs]] -=== Referring beans from Endpoint URIs - -When configuring endpoints using the URI syntax you can refer to beans -in the Registry using the `#bean:id` notation. - -NOTE: The older syntax with just `#id` has been deprecated due to ambiguity -as Camel supports a number of additional functions that start with the # notation. - -If the URI parameter value starts with `#bean:` then Camel will lookup in -the Registry for a bean of the given type by id. For instance: - -[source] ----- -file://inbox?sorter=#bean:mySpecialFileSorter ----- - -Will lookup a bean with the id `mySpecialFileSorter` in the -Registry. - -Camel also supports to refer to beans by their class type. - -[[HowdoIconfigureendpoints-ReferringbeansbyclassfromEndpointURIs]] -=== Referring beans by class from Endpoint URIs - -When configuring endpoints using URI syntax you can now refer to bean by its class name -using the `#class:fullyQualifiedName` notation. - -If the parameter value starts with a `#class:` sign then Camel will load the -class with the given name, and create an instance of the bean using its _no-arg_ constructor: - -[source,text] ----- -file://inbox?sorter=#class:com.foo.MySpecialSorter ----- - -If you need to provide parameters to the constructor, then this is also possible -(limited to numbers, boolean, literal, and null values) - -[source,text] ----- -file://inbox?sorter=#class:com.foo.MySpecialSorter(10, 'Hello world', true) ----- - -[[HowdoIconfigureendpoints-ReferringbeansbytypefromEndpointURIs]] -=== Referring beans by type from Endpoint URIs - -When configuring endpoints using URI syntax you can now refer to bean by its type which -are used to lookup the bean by the given type from the xref:ROOT:registry.adoc[Registry]. -If there is one bean found in the registry of the given type, then that bean instance will be used; -otherwise an exception is thrown. - -[source] ----- -file://inbox?idempontentRepository=#type:org.apache.camel.spi.IdempotentRepository ----- - -[[HowdoIconfigureendpoints-Configuringparametervaluesusingrawvalues,egsuchaspasswords]] -=== Configuring parameter values using raw values, eg such as passwords - -*Since Camel 2.11* - -When configuring endpoint options using URI syntax, then the values is -by default URI encoded. This can be a problem if you want to configure -passwords and just use the value _as is_ without any encoding. For -example you may have a plus sign in the password, which would be decimal -encoded by default. - -So from Camel 2.11 onwards we made this easier as you can denote a -parameter value to be *raw* using the following syntax `RAW(value)`, e.g. -the value starts with `RAW(` and then ends with the parenthesis `)`. -Here is a little example: - -[source,java] ----- -.to("ftp:[email protected]?password=RAW(se+re?t&23)&binary=true") ----- - -In the above example, we have declare the password value as raw, and the -actual password would be as typed, eg `se+re?t&23`. - -NOTE: you may find a corner case when you use both `)` and `&` character as part of your password (ie, `se+re)t&23`). The parser will interpret the `)` as closing the `RAW` function and having a parameter started by `&`. In such case, you can instead use the `RAW{}` notation to let you include the `)` character and have it decoded as part of the password (ie, `RAW{se+re)t&23}`). As a safe alternative you can also use `password=#property:myPass` and then have `myPass` a xref:ROOT:property [...] - -==== Using ENV variables with raw values - -*Since Camel 4.7* - -If you need to use environment variables, for example as username or passwords then this is now possible by inlining -the xref:components:languages:simple-language.adoc[Simple] language -using `+++$simple{xxx}+++` syntax in `RAW(...)` as shown below: - -[source,java] ----- -.to("ftp:[email protected]?password=RAW($simple{env:MY_FTP_PASSWORD})&binary=true") ----- - -[[HowdoIconfigureendpoints-Usingpropertyplaceholders]] -=== Using property placeholders - -Camel has extensive support for using property placeholders, which you -can read more about here. For -example in the ftp example above we can externalize the password to a -`.properties` file. - -For example configuring the property placeholder when using a -XML DSL, where we declare the location of the `.properties` -file. Though we can also define this in Java code. See the -documentation for more details. - -[source,xml] ----- -<camelContext> - <propertyPlaceholder id="properties" location="myftp.properties"/> - ... -</camelContext> ----- - -And the Camel route now refers to the placeholder using the `{\{key}}` -notation: - -[source,java] ----- -.to("ftp:[email protected]?password={{myFtpPassword}}&binary=true" ----- - -And have a `myftp.properties` file with password. Notice we still define -the `RAW(value)` style to ensure the password is used _as is_: - -[source,text] ----- -myFtpPassword=RAW(se+re?t&23) ----- - -We could still have used the `RAW(value)` in the Camel route instead: - -[source,java] ----- -.to("ftp:[email protected]?password=RAW({{myFtpPassword}})&binary=true") ----- - -And then we would need to remove the `RAW` from the properties file: - -[source] ----- -myFtpPassword=se+re?t&23 ----- - -To understand more about property placeholders, read the -documentation. - -In Camel 3.4 you can use an alternative than RAW to refer to a property placeholder by its -key, as discussed in the following section. - -=== Referring to a property placeholder - -When using `{\{key}}` in configuring endpoint URIs then Camel will replace the `{\{key}}` while parsing the endpoint URI. -This has its pros but also a few cons, such as when using sensitive information such as passwords. As we have seen -in the previous section you can use RAW() syntax. Instead of using RAW() you can use `#property:key` notation, -as shown in the example below: - -[source,java] ----- -.to("ftp:[email protected]?password=#property:myFtpPassword&binary=true") ----- - -... and in XML: - -[source,xml] ----- -<to uri="ftp:[email protected]?password=#property:myFtpPassword&binary=true"/> ----- - -[[HowdoIconfigureendpoints-Configuringurisusingendpointwithbeanpropertystyle]] -== Configuring URIs using endpoint with bean property style - -Sometimes configuring endpoint URIs may have many options, and therefore -the URI can become long. In Java DSL you can break the URIs into new -lines as its just Java code, e.g. just concat the `String`. When using XML -DSL then the URI is an attribute, e.g. `<from uri="bla bla"/>`. From Camel -2.15 onwards you can configure the endpoint separately, and from the -routes refer to the endpoints using their shorthand ids. - -[source,xml] ----- -<camelContext> - - <endpoint id="foo" uri="ftp://foo@myserver";> - <property key="password" value="secret"/> - <property key="recursive" value="true"/> - <property key="ftpClient.dataTimeout" value="30000"/> - <property key="ftpClient.serverLanguageCode" value="fr"/> - </endpoint> - - <route> - <from uri="ref:foo"/> - ... - </route> -</camelContext> ----- - -In the example above, the endpoint with id `foo`, is defined using -`<endpoint>` which under the covers assembles this as an URI, with all the -options, as if you have defined all the options directly in the URI. You -can still configure some options in the URI, and then use `<property>` -style for additional options, or to override options from the URI, such -as: - -[source] ----- -<endpoint id="foo" uri="ftp://foo@myserver?recursive=true";> - <property key="password" value="secret"/> - <property key="ftpClient.dataTimeout" value="30000"/> - <property key="ftpClient.serverLanguageCode" value="fr"/> -</endpoint> ----- - -[[HowdoIconfigureendpoints-Configuringlongurisusingnewlines]] -== Configuring long URIs using new lines - -Sometimes configuring endpoint URIs may have many options, and therefore -the URI can become long. In Java DSL you can break the URIs into new -lines as its just Java code, e.g. just concat the `String`. When using XML -DSL then the URI is an attribute, e.g. `<from uri="bla bla"/>`. From Camel -2.15 onwards you can break the URI attribute using new line, such as -shown below: - -[source,xml] ----- -<route> - <from uri="ftp://foo@myserver?password=secret& - recursive=true& - ftpClient.dataTimeout=30000& - ftpClientConfig.serverLanguageCode=fr"/> - <to uri="bean:doSomething"/> -</route> ----- - -Notice that it still requires escaping `&` as `&amp;` in XML. Also you -can have multiple options in one line, eg this is the same: - -[source,xml] ----- -<route> - <from uri="ftp://foo@myserver?password=secret& - recursive=true&ftpClient.dataTimeout=30000& - ftpClientConfig.serverLanguageCode=fr"/> - <to uri="bean:doSomething"/> -</route> ----- - diff --git a/docs/user-manual/modules/faq/pages/how-do-i-configure-password-options-on-camel-endpoints-without-the-value-being-encoded.adoc b/docs/user-manual/modules/faq/pages/how-do-i-configure-password-options-on-camel-endpoints-without-the-value-being-encoded.adoc deleted file mode 100644 index 46e12acbedec..000000000000 --- a/docs/user-manual/modules/faq/pages/how-do-i-configure-password-options-on-camel-endpoints-without-the-value-being-encoded.adoc +++ /dev/null @@ -1,11 +0,0 @@ -= How do I configure password options on Camel endpoints without the value being encoded? - -When you configure Camel endpoints using xref:ROOT:uris.adoc[URIs] then the -parameter values gets url encoded by default. + -This can be a problem when you want to configure passwords _as is_. - -To do that you can tell Camel to use the raw value, by enclosing the -value with RAW(value). See more details at -xref:how-do-i-configure-endpoints.adoc[How do I configure endpoints?] -which has an example also. - diff --git a/docs/user-manual/modules/faq/pages/index.adoc b/docs/user-manual/modules/faq/pages/index.adoc index 60ee1559dcdc..3f75c3aeb317 100644 --- a/docs/user-manual/modules/faq/pages/index.adoc +++ b/docs/user-manual/modules/faq/pages/index.adoc @@ -37,8 +37,6 @@ 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-does-camel-look-up-beans-and-endpoints.adoc[How does Camel look up beans and endpoints?] -* 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?] * xref:how-do-i-configure-the-maximum-endpoint-cache-size-for-camelcontext.adoc[How do I configure the maximum endpoint cache size for CamelContext?] * xref:how-do-i-debug-my-route.adoc[How do I debug my route?] diff --git a/docs/user-manual/modules/faq/pages/why-cant-i-use-sign-in-my-password.adoc b/docs/user-manual/modules/faq/pages/why-cant-i-use-sign-in-my-password.adoc index 039b937ffa2b..77194f3bfd86 100644 --- a/docs/user-manual/modules/faq/pages/why-cant-i-use-sign-in-my-password.adoc +++ b/docs/user-manual/modules/faq/pages/why-cant-i-use-sign-in-my-password.adoc @@ -6,8 +6,4 @@ When you configure Camel endpoints using xref:ROOT:uris.adoc[URIs] then the parameter values gets url encoded by default. This can be a problem when you want to configure passwords _as is_. -To do that you can tell Camel to use the raw value, by enclosing the -value with RAW(value). See more details at -xref:how-do-i-configure-endpoints.adoc[How do I configure endpoints?] -which has an example also.
