You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2026/06/21 07:44:12 UTC
(camel) branch quick-fix/doc-split-broken-fragments created (now 49d7e82a5e44)
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch quick-fix/doc-split-broken-fragments
in repository https://gitbox.apache.org/repos/asf/camel.git
at 49d7e82a5e44 chore: Fix broken fragment links from doc-split
This branch includes the following new commits:
new 49d7e82a5e44 chore: Fix broken fragment links from doc-split
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
(camel) 01/01: chore: Fix broken fragment links from doc-split
Posted by da...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch quick-fix/doc-split-broken-fragments
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 49d7e82a5e44b8b5da631dc7ce5780068adc7e67
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Sun Jun 21 09:43:56 2026 +0200
chore: Fix broken fragment links from doc-split
Replace same-page <<anchor>> references with cross-page xrefs for
anchors that stayed in the parent page after the doc split:
- ibm-watsonx-ai-examples: cos-connection-setup -> main component page
- salesforce-rest-api: apexCall -> main component page
Co-Authored-By: Claude Opus 4.6 <no...@anthropic.com>
Signed-off-by: Claus Ibsen <cl...@gmail.com>
---
.../camel-ibm-watsonx-ai/src/main/docs/ibm-watsonx-ai-examples.adoc | 2 +-
.../camel-salesforce-component/src/main/docs/salesforce-rest-api.adoc | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/components/camel-ibm/camel-ibm-watsonx-ai/src/main/docs/ibm-watsonx-ai-examples.adoc b/components/camel-ibm/camel-ibm-watsonx-ai/src/main/docs/ibm-watsonx-ai-examples.adoc
index 80c4fba20bc6..5b9fd6eaa9df 100644
--- a/components/camel-ibm/camel-ibm-watsonx-ai/src/main/docs/ibm-watsonx-ai-examples.adoc
+++ b/components/camel-ibm/camel-ibm-watsonx-ai/src/main/docs/ibm-watsonx-ai-examples.adoc
@@ -944,7 +944,7 @@ from("azure-storage-blob://mycontainer?prefix=documents/")
Text classification operations allow you to classify documents using IBM watsonx.ai's document processing capabilities. These operations require Cloud Object Storage (COS) configuration.
-IMPORTANT: The COS connection in your watsonx.ai project must be configured with HMAC credentials (access_key_id and secret_access_key), not just IAM Service Credentials. See <<cos-connection-setup>> for details.
+IMPORTANT: The COS connection in your watsonx.ai project must be configured with HMAC credentials (access_key_id and secret_access_key), not just IAM Service Credentials. See xref:ROOT:ibm-watsonx-ai-component.adoc#cos-connection-setup[COS Connection Setup] for details.
==== Classify Documents from Cloud Object Storage
diff --git a/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-rest-api.adoc b/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-rest-api.adoc
index 293d46e6f9e1..971537dd7dbc 100644
--- a/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-rest-api.adoc
+++ b/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-rest-api.adoc
@@ -25,7 +25,7 @@ The following operations are supported:
results) using the result link returned from the 'query' API.
* <<queryAll,queryAll>> - Runs a SOQL query. Unlike the query operation, queryAll returns records that are deleted because of a merge or delete. queryAll also returns information about archived task and event records.
* <<sosl_search,search>> - Runs a Salesforce SOSL query.
-* <<apexCall,apexCall>> - Executes a user defined APEX REST API call.
+* xref:ROOT:salesforce-component.adoc#apexCall[apexCall] - Executes a user defined APEX REST API call.
* <<approval,approval>> - Submits a record or records (batch) for approval process.
* <<approvals,approvals>> - Fetches a list of all approval processes.
* <<composite,composite>> - Executes up to 25 REST API requests in a single call. You can use the output of one