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/07/22 06:37:58 UTC

(camel) branch feature/CAMEL-24233-catalog-docs created (now e9a41c8defec)

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

davsclaus pushed a change to branch feature/CAMEL-24233-catalog-docs
in repository https://gitbox.apache.org/repos/asf/camel.git


      at e9a41c8defec CAMEL-24233: Include AsciiDoc documentation in camel-catalog JAR

This branch includes the following new commits:

     new e9a41c8defec CAMEL-24233: Include AsciiDoc documentation in camel-catalog JAR

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: CAMEL-24233: Include AsciiDoc documentation in camel-catalog JAR

Posted by da...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch feature/CAMEL-24233-catalog-docs
in repository https://gitbox.apache.org/repos/asf/camel.git

commit e9a41c8defecdacc4f43f45b1193986c02837899
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Wed Jul 22 08:37:18 2026 +0200

    CAMEL-24233: Include AsciiDoc documentation in camel-catalog JAR
    
    Co-Authored-By: Claude Opus 4.6 <no...@anthropic.com>
    Signed-off-by: Claus Ibsen <cl...@gmail.com>
---
 .../org/apache/camel/catalog/docs.properties       |  693 +++++++
 .../apache/camel/catalog/docs/a2a-component.adoc   |  766 ++++++++
 .../apache/camel/catalog/docs/a2a-consumer.adoc    |  743 +++++++
 .../apache/camel/catalog/docs/a2a-producer.adoc    |  377 ++++
 .../camel/catalog/docs/activemq-component.adoc     |  144 ++
 .../camel/catalog/docs/activemq6-component.adoc    |  144 ++
 .../apache/camel/catalog/docs/aggregate-eip.adoc   |  816 ++++++++
 .../org/apache/camel/catalog/docs/ai-patterns.adoc |  218 +++
 .../camel/catalog/docs/ai-tool-component.adoc      |  219 +++
 .../apache/camel/catalog/docs/amqp-component.adoc  |  161 ++
 .../camel/catalog/docs/arangodb-component.adoc     |  143 ++
 .../apache/camel/catalog/docs/as2-component.adoc   |   56 +
 .../apache/camel/catalog/docs/asn1-dataformat.adoc |   81 +
 .../camel/catalog/docs/asterisk-component.adoc     |  131 ++
 .../docs/atmosphere-websocket-component.adoc       |  124 ++
 .../apache/camel/catalog/docs/atom-component.adoc  |  235 +++
 .../org/apache/camel/catalog/docs/attachments.adoc |   34 +
 .../apache/camel/catalog/docs/avro-component.adoc  |  355 ++++
 .../apache/camel/catalog/docs/avro-dataformat.adoc |  122 ++
 .../catalog/docs/avroJackson2-dataformat.adoc      |  100 +
 .../catalog/docs/avroJackson3-dataformat.adoc      |  100 +
 .../catalog/docs/aws-bedrock-agent-component.adoc  |   89 +
 .../docs/aws-bedrock-agent-runtime-component.adoc  |  157 ++
 .../camel/catalog/docs/aws-bedrock-component.adoc  |  298 +++
 .../camel/catalog/docs/aws-bedrock-examples.adoc   | 1148 +++++++++++
 .../camel/catalog/docs/aws-bedrock-models.adoc     |  604 ++++++
 .../catalog/docs/aws-cloudtrail-component.adoc     |   76 +
 .../camel/catalog/docs/aws-config-component.adoc   |   69 +
 .../docs/aws-secrets-manager-component.adoc        |  564 ++++++
 .../catalog/docs/aws-security-hub-component.adoc   |  239 +++
 .../camel/catalog/docs/aws2-athena-component.adoc  |  976 ++++++++++
 .../catalog/docs/aws2-comprehend-component.adoc    |  678 +++++++
 .../camel/catalog/docs/aws2-cw-component.adoc      |  180 ++
 .../camel/catalog/docs/aws2-ddb-component.adoc     |  305 +++
 .../catalog/docs/aws2-ddbstream-component.adoc     |  117 ++
 .../camel/catalog/docs/aws2-ec2-component.adoc     |  224 +++
 .../camel/catalog/docs/aws2-ecs-component.adoc     |  151 ++
 .../camel/catalog/docs/aws2-eks-component.adoc     |  155 ++
 .../catalog/docs/aws2-eventbridge-component.adoc   |  841 ++++++++
 .../camel/catalog/docs/aws2-iam-component.adoc     | 1365 +++++++++++++
 .../camel/catalog/docs/aws2-kinesis-component.adoc |  229 +++
 .../docs/aws2-kinesis-firehose-component.adoc      |  171 ++
 .../camel/catalog/docs/aws2-kms-component.adoc     |  283 +++
 .../camel/catalog/docs/aws2-lambda-component.adoc  |  860 ++++++++
 .../camel/catalog/docs/aws2-mq-component.adoc      |  264 +++
 .../camel/catalog/docs/aws2-msk-component.adoc     |  222 +++
 .../camel/catalog/docs/aws2-polly-component.adoc   |  205 ++
 .../catalog/docs/aws2-redshift-data-component.adoc |  164 ++
 .../catalog/docs/aws2-rekognition-component.adoc   |  180 ++
 .../camel/catalog/docs/aws2-s3-component.adoc      |  392 ++++
 .../catalog/docs/aws2-s3-consumer-examples.adoc    |  313 +++
 .../catalog/docs/aws2-s3-producer-operations.adoc  |  478 +++++
 .../camel/catalog/docs/aws2-s3-streaming.adoc      |  303 +++
 .../catalog/docs/aws2-s3-vectors-component.adoc    |  237 +++
 .../camel/catalog/docs/aws2-ses-component.adoc     |  189 ++
 .../camel/catalog/docs/aws2-sns-component.adoc     |  340 ++++
 .../camel/catalog/docs/aws2-sqs-component.adoc     |  461 +++++
 .../docs/aws2-step-functions-component.adoc        |  174 ++
 .../camel/catalog/docs/aws2-sts-component.adoc     |  255 +++
 .../catalog/docs/aws2-textract-component.adoc      |   88 +
 .../catalog/docs/aws2-timestream-component.adoc    |  273 +++
 .../catalog/docs/aws2-transcribe-component.adoc    |   88 +
 .../catalog/docs/aws2-translate-component.adoc     |  126 ++
 .../catalog/docs/azure-cosmosdb-component.adoc     |  892 +++++++++
 .../catalog/docs/azure-eventhubs-component.adoc    |  217 +++
 .../camel/catalog/docs/azure-files-component.adoc  |  363 ++++
 .../catalog/docs/azure-functions-component.adoc    |  453 +++++
 .../catalog/docs/azure-key-vault-component.adoc    |  809 ++++++++
 .../camel/catalog/docs/azure-schema-registry.adoc  |   15 +
 .../catalog/docs/azure-servicebus-component.adoc   |  242 +++
 .../catalog/docs/azure-storage-blob-component.adoc |  264 +++
 .../catalog/docs/azure-storage-blob-consumer.adoc  |  282 +++
 .../docs/azure-storage-blob-operations.adoc        |  641 ++++++
 .../docs/azure-storage-datalake-component.adoc     |  808 ++++++++
 .../docs/azure-storage-queue-component.adoc        |  658 +++++++
 .../camel/catalog/docs/barcode-dataformat.adoc     |  138 ++
 .../camel/catalog/docs/base64-dataformat.adoc      |  179 ++
 .../apache/camel/catalog/docs/batchConfig-eip.adoc |   18 +
 .../apache/camel/catalog/docs/bean-component.adoc  |  146 ++
 .../org/apache/camel/catalog/docs/bean-eip.adoc    |  183 ++
 .../apache/camel/catalog/docs/bean-language.adoc   |  143 ++
 .../catalog/docs/bean-validator-component.adoc     |  362 ++++
 .../camel/catalog/docs/beanio-dataformat.adoc      |  152 ++
 .../camel/catalog/docs/bindy-dataformat.adoc       | 2050 ++++++++++++++++++++
 .../camel/catalog/docs/bonita-component.adoc       |   97 +
 .../apache/camel/catalog/docs/box-component.adoc   |  166 ++
 .../camel/catalog/docs/braintree-component.adoc    |   89 +
 .../camel/catalog/docs/browse-component.adoc       |   92 +
 .../catalog/docs/caffeine-cache-component.adoc     |  107 +
 .../catalog/docs/caffeine-loadcache-component.adoc |   44 +
 .../camel/catalog/docs/camunda-component.adoc      |  512 +++++
 .../apache/camel/catalog/docs/cbor-dataformat.adoc |  127 ++
 .../camel/catalog/docs/change-data-capture.adoc    |   18 +
 .../apache/camel/catalog/docs/channel-adapter.adoc |   86 +
 .../camel/catalog/docs/chatscript-component.adoc   |   43 +
 .../org/apache/camel/catalog/docs/choice-eip.adoc  |  286 +++
 .../apache/camel/catalog/docs/chunk-component.adoc |  263 +++
 .../camel/catalog/docs/circuitBreaker-eip.adoc     |  111 ++
 .../apache/camel/catalog/docs/claimCheck-eip.adoc  |  453 +++++
 .../apache/camel/catalog/docs/class-component.adoc |  217 +++
 .../apache/camel/catalog/docs/cli-connector.adoc   |   28 +
 .../org/apache/camel/catalog/docs/cli-debug.adoc   |   53 +
 .../camel/catalog/docs/clickup-component.adoc      |   78 +
 .../org/apache/camel/catalog/docs/cloudevents.adoc |   15 +
 .../camel/catalog/docs/cm-sms-component.adoc       |   36 +
 .../apache/camel/catalog/docs/coap-component.adoc  |  533 +++++
 .../camel/catalog/docs/cometd-component.adoc       |  138 ++
 .../camel/catalog/docs/competing-consumers.adoc    |  187 ++
 .../catalog/docs/composed-message-processor.adoc   |   98 +
 .../camel/catalog/docs/constant-language.adoc      |  137 ++
 .../camel/catalog/docs/consul-component.adoc       |  111 ++
 .../camel/catalog/docs/content-enricher.adoc       |  261 +++
 .../camel/catalog/docs/content-filter-eip.adoc     |  189 ++
 .../camel/catalog/docs/controlbus-component.adoc   |  150 ++
 .../camel/catalog/docs/convertBodyTo-eip.adoc      |   64 +
 .../camel/catalog/docs/convertHeaderTo-eip.adoc    |  162 ++
 .../camel/catalog/docs/convertVariableTo-eip.adoc  |  162 ++
 .../camel/catalog/docs/correlation-identifier.adoc |   86 +
 .../camel/catalog/docs/couchbase-component.adoc    |  203 ++
 .../camel/catalog/docs/couchdb-component.adoc      |  206 ++
 .../apache/camel/catalog/docs/cql-component.adoc   |  203 ++
 .../apache/camel/catalog/docs/cron-component.adoc  |  116 ++
 .../camel/catalog/docs/crypto-component.adoc       |  693 +++++++
 .../camel/catalog/docs/crypto-dataformat.adoc      |  283 +++
 .../apache/camel/catalog/docs/csimple-joor.adoc    |   50 +
 .../camel/catalog/docs/csimple-language.adoc       |  298 +++
 .../apache/camel/catalog/docs/csv-dataformat.adoc  |  597 ++++++
 .../camel/catalog/docs/customLoadBalancer-eip.adoc |  111 ++
 .../apache/camel/catalog/docs/cxf-component.adoc   | 1185 +++++++++++
 .../apache/camel/catalog/docs/cxfrs-component.adoc |  462 +++++
 .../catalog/docs/cyberark-vault-component.adoc     |  724 +++++++
 .../apache/camel/catalog/docs/dapr-component.adoc  | 1088 +++++++++++
 .../camel/catalog/docs/dataformat-component.adoc   |   80 +
 .../camel/catalog/docs/dataset-component.adoc      |  215 ++
 .../camel/catalog/docs/dataset-test-component.adoc |  101 +
 .../camel/catalog/docs/datasonnet-language.adoc    |  452 +++++
 .../camel/catalog/docs/dead-letter-channel.adoc    |  647 ++++++
 .../camel/catalog/docs/debezium-db2-component.adoc |  176 ++
 .../catalog/docs/debezium-mongodb-component.adoc   |  177 ++
 .../catalog/docs/debezium-mysql-component.adoc     |  192 ++
 .../catalog/docs/debezium-oracle-component.adoc    |  174 ++
 .../catalog/docs/debezium-postgres-component.adoc  |  174 ++
 .../catalog/docs/debezium-sqlserver-component.adoc |  173 ++
 .../org/apache/camel/catalog/docs/debug.adoc       |   40 +
 .../org/apache/camel/catalog/docs/delay-eip.adoc   |  241 +++
 .../apache/camel/catalog/docs/dfdl-component.adoc  |  124 ++
 .../apache/camel/catalog/docs/dfdl-dataformat.adoc |  100 +
 .../apache/camel/catalog/docs/dhis2-component.adoc |  470 +++++
 .../org/apache/camel/catalog/docs/diagram.adoc     |  426 ++++
 .../camel/catalog/docs/digitalocean-component.adoc |  598 ++++++
 .../camel/catalog/docs/direct-component.adoc       |  109 ++
 .../camel/catalog/docs/disruptor-component.adoc    |  300 +++
 .../camel/catalog/docs/disruptor-vm-component.adoc |   93 +
 .../apache/camel/catalog/docs/djl-component.adoc   |  574 ++++++
 .../apache/camel/catalog/docs/dns-component.adoc   |  239 +++
 .../camel/catalog/docs/docker-component.adoc       |  146 ++
 .../catalog/docs/docling-async-processing.adoc     |  401 ++++
 .../catalog/docs/docling-batch-processing.adoc     |  700 +++++++
 .../camel/catalog/docs/docling-component.adoc      | 1290 ++++++++++++
 .../apache/camel/catalog/docs/docling-serve.adoc   |  351 ++++
 .../apache/camel/catalog/docs/drill-component.adoc |   51 +
 .../camel/catalog/docs/dropbox-component.adoc      |  776 ++++++++
 .../apache/camel/catalog/docs/dsl-modeline.adoc    |   17 +
 .../camel/catalog/docs/durable-subscriber.adoc     |   85 +
 .../catalog/docs/dynamic-router-component.adoc     |  522 +++++
 .../docs/dynamic-router-control-component.adoc     |  337 ++++
 .../camel/catalog/docs/dynamicRouter-eip.adoc      |  191 ++
 .../camel/catalog/docs/ehcache-component.adoc      |  135 ++
 .../camel/catalog/docs/eip-exchangeProperties.adoc |   26 +
 .../org/apache/camel/catalog/docs/eip-options.adoc |   16 +
 .../catalog/docs/elasticsearch-component.adoc      |  450 +++++
 .../docs/elasticsearch-rest-client-component.adoc  |  425 ++++
 .../org/apache/camel/catalog/docs/enrich-eip.adoc  |  278 +++
 .../docs/enterprise-integration-patterns.adoc      |  467 +++++
 .../apache/camel/catalog/docs/event-component.adoc |  872 +++++++++
 .../apache/camel/catalog/docs/event-message.adoc   |  192 ++
 .../catalog/docs/eventDrivenConsumer-eip.adoc      |   58 +
 .../catalog/docs/exchangeProperty-language.adoc    |   67 +
 .../apache/camel/catalog/docs/exec-component.adoc  |  343 ++++
 .../catalog/docs/failoverLoadBalancer-eip.adoc     |  285 +++
 .../camel/catalog/docs/fastjson-dataformat.adoc    |   77 +
 .../camel/catalog/docs/fault-tolerance-eip.adoc    |  269 +++
 .../docs/faultToleranceConfiguration-eip.adoc      |   22 +
 .../apache/camel/catalog/docs/fhir-component.adoc  |   70 +
 .../camel/catalog/docs/fhirJson-dataformat.adoc    |   20 +
 .../camel/catalog/docs/fhirXml-dataformat.adoc     |   20 +
 .../apache/camel/catalog/docs/file-component.adoc  | 1826 +++++++++++++++++
 .../apache/camel/catalog/docs/file-language.adoc   |  222 +++
 .../camel/catalog/docs/file-watch-component.adoc   |  148 ++
 .../org/apache/camel/catalog/docs/filter-eip.adoc  |  313 +++
 .../camel/catalog/docs/flatpack-component.adoc     |  267 +++
 .../camel/catalog/docs/flatpack-dataformat.adoc    |   86 +
 .../apache/camel/catalog/docs/flink-component.adoc |  423 ++++
 .../camel/catalog/docs/flowable-component.adoc     |   90 +
 .../apache/camel/catalog/docs/fop-component.adoc   |  171 ++
 .../apache/camel/catalog/docs/fory-dataformat.adoc |   45 +
 .../camel/catalog/docs/freemarker-component.adoc   |  340 ++++
 .../org/apache/camel/catalog/docs/from-eip.adoc    |   64 +
 .../apache/camel/catalog/docs/ftp-component.adoc   |  960 +++++++++
 .../apache/camel/catalog/docs/ftps-component.adoc  |   41 +
 .../camel/catalog/docs/geocoder-component.adoc     |  197 ++
 .../apache/camel/catalog/docs/git-component.adoc   |  165 ++
 .../camel/catalog/docs/github2-component.adoc      |  254 +++
 .../catalog/docs/google-bigquery-component.adoc    |  135 ++
 .../docs/google-bigquery-sql-component.adoc        |  218 +++
 .../catalog/docs/google-calendar-component.adoc    |   66 +
 .../docs/google-calendar-stream-component.adoc     |   66 +
 .../camel/catalog/docs/google-drive-component.adoc |   80 +
 .../catalog/docs/google-firestore-component.adoc   | 1175 +++++++++++
 .../catalog/docs/google-functions-component.adoc   |  554 ++++++
 .../camel/catalog/docs/google-mail-component.adoc  |  316 +++
 .../catalog/docs/google-mail-stream-component.adoc |   66 +
 .../catalog/docs/google-pubsub-component.adoc      |  234 +++
 .../docs/google-secret-manager-component.adoc      |  813 ++++++++
 .../catalog/docs/google-sheets-component.adoc      |   97 +
 .../docs/google-sheets-stream-component.adoc       |   84 +
 .../docs/google-speech-to-text-component.adoc      |  345 ++++
 .../catalog/docs/google-storage-component.adoc     |  637 ++++++
 .../docs/google-text-to-speech-component.adoc      |  421 ++++
 .../catalog/docs/google-vertexai-component.adoc    |  585 ++++++
 .../catalog/docs/google-vision-component.adoc      |  540 ++++++
 .../camel/catalog/docs/graphql-component.adoc      |  329 ++++
 .../apache/camel/catalog/docs/grok-dataformat.adoc |  160 ++
 .../apache/camel/catalog/docs/groovy-language.adoc |  198 ++
 .../camel/catalog/docs/groovyJson-dataformat.adoc  |  102 +
 .../camel/catalog/docs/groovyXml-dataformat.adoc   |   93 +
 .../apache/camel/catalog/docs/grpc-component.adoc  |  576 ++++++
 .../apache/camel/catalog/docs/gson-dataformat.adoc |   77 +
 .../camel/catalog/docs/guaranteed-delivery.adoc    |   63 +
 .../catalog/docs/gzipDeflater-dataformat.adoc      |   98 +
 .../catalog/docs/hashicorp-vault-component.adoc    |  472 +++++
 .../docs/hazelcast-atomicvalue-component.adoc      |  270 +++
 .../catalog/docs/hazelcast-instance-component.adoc |   97 +
 .../catalog/docs/hazelcast-list-component.adoc     |  298 +++
 .../catalog/docs/hazelcast-map-component.adoc      |  479 +++++
 .../catalog/docs/hazelcast-multimap-component.adoc |  314 +++
 .../docs/hazelcast-pncounter-component.adoc        |  265 +++
 .../catalog/docs/hazelcast-queue-component.adoc    |  678 +++++++
 .../docs/hazelcast-replicatedmap-component.adoc    |  225 +++
 .../docs/hazelcast-ringbuffer-component.adoc       |  127 ++
 .../catalog/docs/hazelcast-seda-component.adoc     |  103 +
 .../catalog/docs/hazelcast-set-component.adoc      |   37 +
 .../camel/catalog/docs/hazelcast-summary.adoc      |  139 ++
 .../catalog/docs/hazelcast-topic-component.adoc    |  135 ++
 .../apache/camel/catalog/docs/header-language.adoc |   67 +
 .../org/apache/camel/catalog/docs/headersmap.adoc  |   34 +
 .../apache/camel/catalog/docs/hl7-dataformat.adoc  |  497 +++++
 .../camel/catalog/docs/hl7terser-language.adoc     |  157 ++
 .../apache/camel/catalog/docs/http-component.adoc  |  937 +++++++++
 .../camel/catalog/docs/huggingface-component.adoc  |  330 ++++
 .../camel/catalog/docs/hwcloud-dms-component.adoc  |  278 +++
 .../camel/catalog/docs/hwcloud-frs-component.adoc  |  254 +++
 .../docs/hwcloud-functiongraph-component.adoc      |  152 ++
 .../camel/catalog/docs/hwcloud-iam-component.adoc  |  257 +++
 .../docs/hwcloud-imagerecognition-component.adoc   |  211 ++
 .../camel/catalog/docs/hwcloud-obs-component.adoc  |  270 +++
 .../camel/catalog/docs/hwcloud-smn-component.adoc  |  203 ++
 .../camel/catalog/docs/ibm-cos-component.adoc      | 1001 ++++++++++
 .../docs/ibm-secrets-manager-component.adoc        |  707 +++++++
 .../docs/ibm-watson-discovery-component.adoc       |  385 ++++
 .../docs/ibm-watson-language-component.adoc        |  352 ++++
 .../docs/ibm-watson-speech-to-text-component.adoc  |  606 ++++++
 .../docs/ibm-watson-text-to-speech-component.adoc  |  571 ++++++
 .../catalog/docs/ibm-watsonx-ai-component.adoc     |  399 ++++
 .../catalog/docs/ibm-watsonx-ai-examples.adoc      | 1571 +++++++++++++++
 .../catalog/docs/ibm-watsonx-data-component.adoc   |  359 ++++
 .../apache/camel/catalog/docs/ical-dataformat.adoc |  104 +
 .../camel/catalog/docs/idempotentConsumer-eip.adoc |   62 +
 .../catalog/docs/iec60870-client-component.adoc    |  300 +++
 .../catalog/docs/iec60870-server-component.adoc    |   48 +
 .../apache/camel/catalog/docs/iggy-component.adoc  |  189 ++
 .../camel/catalog/docs/ignite-cache-component.adoc |   29 +
 .../catalog/docs/ignite-compute-component.adoc     |   43 +
 .../catalog/docs/ignite-events-component.adoc      |   27 +
 .../camel/catalog/docs/ignite-idgen-component.adoc |   24 +
 .../catalog/docs/ignite-messaging-component.adoc   |   24 +
 .../camel/catalog/docs/ignite-queue-component.adoc |   24 +
 .../camel/catalog/docs/ignite-set-component.adoc   |   24 +
 .../apache/camel/catalog/docs/ignite-summary.adoc  |   96 +
 .../camel/catalog/docs/infinispan-component.adoc   |  591 ++++++
 .../docs/infinispan-embedded-component.adoc        |  438 +++++
 .../camel/catalog/docs/influxdb-component.adoc     |   92 +
 .../camel/catalog/docs/influxdb2-component.adoc    |   87 +
 .../org/apache/camel/catalog/docs/intercept.adoc   |  855 ++++++++
 .../apache/camel/catalog/docs/irc-component.adoc   |  161 ++
 .../camel/catalog/docs/ironmq-component.adoc       |  141 ++
 .../camel/catalog/docs/iso8583-dataformat.adoc     |  216 +++
 .../camel/catalog/docs/jackson2-dataformat.adoc    |  120 ++
 .../camel/catalog/docs/jackson3-dataformat.adoc    |  147 ++
 .../camel/catalog/docs/jacksonXml2-dataformat.adoc |  455 +++++
 .../camel/catalog/docs/jacksonXml3-dataformat.adoc |  455 +++++
 .../org/apache/camel/catalog/docs/jandex.adoc      |   15 +
 .../org/apache/camel/catalog/docs/jasypt.adoc      |  251 +++
 .../apache/camel/catalog/docs/java-joor-dsl.adoc   |   55 +
 .../apache/camel/catalog/docs/java-language.adoc   |  386 ++++
 .../apache/camel/catalog/docs/java-xml-io-dsl.adoc |  305 +++
 .../camel/catalog/docs/java-xml-jaxb-dsl.adoc      |   28 +
 .../apache/camel/catalog/docs/jaxb-dataformat.adoc |  299 +++
 .../camel/catalog/docs/jcache-component.adoc       |  346 ++++
 .../apache/camel/catalog/docs/jcr-component.adoc   |  148 ++
 .../apache/camel/catalog/docs/jdbc-component.adoc  |  337 ++++
 .../apache/camel/catalog/docs/jetty-component.adoc |  848 ++++++++
 .../org/apache/camel/catalog/docs/jfr.adoc         |   30 +
 .../camel/catalog/docs/jgroups-component.adoc      |  230 +++
 .../camel/catalog/docs/jgroups-raft-component.adoc |  187 ++
 .../apache/camel/catalog/docs/jira-component.adoc  |  237 +++
 .../apache/camel/catalog/docs/jms-component.adoc   | 1521 +++++++++++++++
 .../apache/camel/catalog/docs/jmx-component.adoc   |   32 +
 .../apache/camel/catalog/docs/jolt-component.adoc  |  174 ++
 .../apache/camel/catalog/docs/jooq-component.adoc  |  253 +++
 .../apache/camel/catalog/docs/joor-language.adoc   |  415 ++++
 .../apache/camel/catalog/docs/jpa-component.adoc   |  585 ++++++
 .../org/apache/camel/catalog/docs/jq-language.adoc |  221 +++
 .../org/apache/camel/catalog/docs/js-language.adoc |   58 +
 .../apache/camel/catalog/docs/jslt-component.adoc  |  283 +++
 .../camel/catalog/docs/json-patch-component.adoc   |   48 +
 .../catalog/docs/json-validator-component.adoc     |  136 ++
 .../camel/catalog/docs/jsonApi-dataformat.adoc     |   33 +
 .../camel/catalog/docs/jsonata-component.adoc      |  187 ++
 .../camel/catalog/docs/jsonb-dataformat.adoc       |   89 +
 .../camel/catalog/docs/jsonpath-language.adoc      |  456 +++++
 .../org/apache/camel/catalog/docs/jsoup.adoc       |   15 +
 .../apache/camel/catalog/docs/jt400-component.adoc |  380 ++++
 .../org/apache/camel/catalog/docs/jta.adoc         |   14 +
 .../apache/camel/catalog/docs/jte-component.adoc   |  133 ++
 .../apache/camel/catalog/docs/kafka-component.adoc | 1601 +++++++++++++++
 .../camel/catalog/docs/kamelet-component.adoc      |  234 +++
 .../org/apache/camel/catalog/docs/kamelet-eip.adoc |  215 ++
 .../camel/catalog/docs/kamelet-main-support.adoc   |   14 +
 .../apache/camel/catalog/docs/kamelet-main.adoc    |   32 +
 .../camel/catalog/docs/keycloak-component.adoc     |  456 +++++
 .../camel/catalog/docs/keycloak-consumer.adoc      |  913 +++++++++
 .../camel/catalog/docs/keycloak-producer.adoc      |  807 ++++++++
 .../camel/catalog/docs/keycloak-security.adoc      | 1118 +++++++++++
 .../camel/catalog/docs/knative-component.adoc      |  386 ++++
 .../camel/catalog/docs/kserve-component.adoc       |  481 +++++
 .../docs/kubernetes-config-maps-component.adoc     |  274 +++
 .../catalog/docs/kubernetes-cronjob-component.adoc |   35 +
 .../kubernetes-custom-resources-component.adoc     |   36 +
 .../docs/kubernetes-deployments-component.adoc     |  147 ++
 .../catalog/docs/kubernetes-events-component.adoc  |  316 +++
 .../catalog/docs/kubernetes-hpa-component.adoc     |  147 ++
 .../catalog/docs/kubernetes-job-component.adoc     |  141 ++
 .../docs/kubernetes-namespaces-component.adoc      |  146 ++
 .../catalog/docs/kubernetes-nodes-component.adoc   |  147 ++
 ...rnetes-persistent-volumes-claims-component.adoc |  103 +
 .../kubernetes-persistent-volumes-component.adoc   |  100 +
 .../catalog/docs/kubernetes-pods-component.adoc    |  149 ++
 ...bernetes-replication-controllers-component.adoc |  151 ++
 .../docs/kubernetes-resources-quota-component.adoc |  103 +
 .../catalog/docs/kubernetes-secrets-component.adoc |  300 +++
 .../kubernetes-service-accounts-component.adoc     |  103 +
 .../docs/kubernetes-services-component.adoc        |  148 ++
 .../camel/catalog/docs/kubernetes-summary.adoc     |  127 ++
 .../apache/camel/catalog/docs/kudu-component.adoc  |   57 +
 .../catalog/docs/langchain4j-agent-component.adoc  | 1139 +++++++++++
 .../catalog/docs/langchain4j-agent-guardrails.adoc |  670 +++++++
 .../camel/catalog/docs/langchain4j-agent-mcp.adoc  |  346 ++++
 .../catalog/docs/langchain4j-agent-multimodal.adoc |  295 +++
 .../catalog/docs/langchain4j-chat-component.adoc   |  325 ++++
 .../docs/langchain4j-embeddings-component.adoc     |  396 ++++
 .../docs/langchain4j-embeddingstore-component.adoc |  249 +++
 .../camel/catalog/docs/langchain4j-tokenizer.adoc  |  138 ++
 .../catalog/docs/langchain4j-tools-component.adoc  |  696 +++++++
 .../docs/langchain4j-web-search-component.adoc     |  212 ++
 .../camel/catalog/docs/language-component.adoc     |  297 +++
 .../apache/camel/catalog/docs/ldap-component.adoc  |  434 +++++
 .../apache/camel/catalog/docs/ldif-component.adoc  |  132 ++
 .../org/apache/camel/catalog/docs/leveldb.adoc     |  197 ++
 .../apache/camel/catalog/docs/loadBalance-eip.adoc |   25 +
 .../apache/camel/catalog/docs/log-component.adoc   |  408 ++++
 .../org/apache/camel/catalog/docs/log-eip.adoc     |  515 +++++
 .../org/apache/camel/catalog/docs/loop-eip.adoc    |  313 +++
 .../apache/camel/catalog/docs/lpr-component.adoc   |  200 ++
 .../org/apache/camel/catalog/docs/lra.adoc         |   25 +
 .../camel/catalog/docs/lucene-component.adoc       |  219 +++
 .../camel/catalog/docs/lumberjack-component.adoc   |   94 +
 .../apache/camel/catalog/docs/lzf-dataformat.adoc  |  125 ++
 .../apache/camel/catalog/docs/mail-component.adoc  |  909 +++++++++
 .../camel/catalog/docs/mail-microsoft-oauth.adoc   |   82 +
 .../org/apache/camel/catalog/docs/main.adoc        | 1230 ++++++++++++
 .../camel/catalog/docs/mapstruct-component.adoc    |   98 +
 .../org/apache/camel/catalog/docs/marshal-eip.adoc |   78 +
 .../camel/catalog/docs/master-component.adoc       |  166 ++
 .../org/apache/camel/catalog/docs/mdc.adoc         |   75 +
 .../apache/camel/catalog/docs/message-broker.adoc  |   20 +
 .../org/apache/camel/catalog/docs/message-bus.adoc |   50 +
 .../apache/camel/catalog/docs/message-channel.adoc |   58 +
 .../camel/catalog/docs/message-dispatcher.adoc     |   16 +
 .../camel/catalog/docs/message-endpoint.adoc       |   62 +
 .../camel/catalog/docs/message-expiration.adoc     |   56 +
 .../apache/camel/catalog/docs/message-history.adoc |  440 +++++
 .../apache/camel/catalog/docs/message-router.adoc  |   93 +
 .../camel/catalog/docs/message-translator.adoc     |  221 +++
 .../org/apache/camel/catalog/docs/message.adoc     |   26 +
 .../camel/catalog/docs/messaging-bridge.adoc       |   55 +
 .../camel/catalog/docs/messaging-gateway.adoc      |   17 +
 .../camel/catalog/docs/messaging-mapper.adoc       |   23 +
 .../camel/catalog/docs/metrics-component.adoc      | 1080 +++++++++++
 .../camel/catalog/docs/micrometer-component.adoc   |  986 ++++++++++
 .../catalog/docs/micrometer-observability.adoc     |  198 ++
 .../camel/catalog/docs/micrometer-prometheus.adoc  |   58 +
 .../camel/catalog/docs/microprofile-config.adoc    |   28 +
 .../catalog/docs/microprofile-fault-tolerance.adoc |   27 +
 .../camel/catalog/docs/microprofile-health.adoc    |   70 +
 .../camel/catalog/docs/milo-browse-component.adoc  |   94 +
 .../camel/catalog/docs/milo-client-component.adoc  |  212 ++
 .../camel/catalog/docs/milo-server-component.adoc  |   67 +
 .../camel/catalog/docs/milvus-component.adoc       |  215 ++
 .../catalog/docs/mimeMultipart-dataformat.adoc     |  189 ++
 .../apache/camel/catalog/docs/mina-component.adoc  |  291 +++
 .../catalog/docs/mina-sftp-authentication.adoc     |  208 ++
 .../camel/catalog/docs/mina-sftp-component.adoc    |  602 ++++++
 .../camel/catalog/docs/mina-sftp-migration.adoc    |  173 ++
 .../camel/catalog/docs/mina-sftp-security.adoc     |  346 ++++
 .../apache/camel/catalog/docs/minio-component.adoc |  723 +++++++
 .../apache/camel/catalog/docs/mllp-component.adoc  |  111 ++
 .../apache/camel/catalog/docs/mock-component.adoc  |  556 ++++++
 .../camel/catalog/docs/mongodb-component.adoc      | 1364 +++++++++++++
 .../catalog/docs/mongodb-gridfs-component.adoc     |  191 ++
 .../apache/camel/catalog/docs/multicast-eip.adoc   |  414 ++++
 .../camel/catalog/docs/mustache-component.adoc     |  223 +++
 .../apache/camel/catalog/docs/mvel-component.adoc  |  217 +++
 .../apache/camel/catalog/docs/mvel-language.adoc   |  142 ++
 .../camel/catalog/docs/mybatis-bean-component.adoc |  130 ++
 .../camel/catalog/docs/mybatis-component.adoc      |  745 +++++++
 .../apache/camel/catalog/docs/nats-component.adoc  |  294 +++
 .../apache/camel/catalog/docs/neo4j-component.adoc |  306 +++
 .../apache/camel/catalog/docs/netty-component.adoc |  752 +++++++
 .../camel/catalog/docs/netty-http-component.adoc   |  705 +++++++
 .../org/apache/camel/catalog/docs/normalizer.adoc  |  119 ++
 .../camel/catalog/docs/oaipmh-component.adoc       |  127 ++
 .../org/apache/camel/catalog/docs/oauth.adoc       |  511 +++++
 .../camel/catalog/docs/observability-services.adoc |  157 ++
 .../org/apache/camel/catalog/docs/observation.adoc |   92 +
 .../apache/camel/catalog/docs/ocsf-dataformat.adoc |  523 +++++
 .../apache/camel/catalog/docs/ognl-language.adoc   |  142 ++
 .../camel/catalog/docs/olingo2-component.adoc      |  225 +++
 .../camel/catalog/docs/olingo4-component.adoc      |  206 ++
 .../apache/camel/catalog/docs/onFallback-eip.adoc  |   31 +
 .../apache/camel/catalog/docs/once-component.adoc  |  261 +++
 .../camel/catalog/docs/openai-component.adoc       | 1026 ++++++++++
 .../org/apache/camel/catalog/docs/openai-mcp.adoc  |  528 +++++
 .../camel/catalog/docs/openai-operations.adoc      |  458 +++++
 .../camel/catalog/docs/openai-providers.adoc       |  250 +++
 .../apache/camel/catalog/docs/openapi-java.adoc    |  188 ++
 .../camel/catalog/docs/openapi-validator.adoc      |   82 +
 .../camel/catalog/docs/opensearch-component.adoc   |  427 ++++
 .../docs/openshift-build-configs-component.adoc    |  100 +
 .../catalog/docs/openshift-builds-component.adoc   |  100 +
 .../openshift-deploymentconfigs-component.adoc     |  148 ++
 .../catalog/docs/openstack-cinder-component.adoc   |   94 +
 .../catalog/docs/openstack-glance-component.adoc   |   69 +
 .../catalog/docs/openstack-keystone-component.adoc |  161 ++
 .../catalog/docs/openstack-neutron-component.adoc  |  133 ++
 .../catalog/docs/openstack-nova-component.adoc     |  108 ++
 .../camel/catalog/docs/openstack-summary.adoc      |   34 +
 .../catalog/docs/openstack-swift-component.adoc    |  102 +
 .../docs/opentelemetry-metrics-component.adoc      |  803 ++++++++
 .../apache/camel/catalog/docs/opentelemetry.adoc   |  192 ++
 .../apache/camel/catalog/docs/opentelemetry2.adoc  |  385 ++++
 .../camel/catalog/docs/optaplanner-component.adoc  |  139 ++
 .../apache/camel/catalog/docs/paho-component.adoc  |  233 +++
 .../camel/catalog/docs/paho-mqtt5-component.adoc   |  233 +++
 .../camel/catalog/docs/parquetAvro-dataformat.adoc |   64 +
 .../apache/camel/catalog/docs/pdf-component.adoc   |   99 +
 .../docs/pg-replication-slot-component.adoc        |   98 +
 .../camel/catalog/docs/pgevent-component.adoc      |   56 +
 .../apache/camel/catalog/docs/pgp-dataformat.adoc  |  347 ++++
 .../camel/catalog/docs/pgvector-component.adoc     |  217 +++
 .../camel/catalog/docs/pinecone-component.adoc     |   34 +
 .../apache/camel/catalog/docs/pipeline-eip.adoc    |  214 ++
 .../catalog/docs/platform-http-component.adoc      |  214 ++
 .../camel/catalog/docs/platform-http-jolokia.adoc  |   49 +
 .../camel/catalog/docs/platform-http-main.adoc     |   71 +
 .../camel/catalog/docs/platform-http-vertx.adoc    |  176 ++
 .../apache/camel/catalog/docs/plc4x-component.adoc |   90 +
 .../camel/catalog/docs/point-to-point-channel.adoc |   78 +
 .../org/apache/camel/catalog/docs/poll-eip.adoc    |  211 ++
 .../apache/camel/catalog/docs/pollEnrich-eip.adoc  |  282 +++
 .../camel/catalog/docs/polling-consumer.adoc       |  102 +
 .../apache/camel/catalog/docs/pqc-component.adoc   |  603 ++++++
 .../apache/camel/catalog/docs/pqc-dataformat.adoc  |  529 +++++
 .../org/apache/camel/catalog/docs/pqc-hybrid.adoc  |  407 ++++
 .../camel/catalog/docs/pqc-key-lifecycle.adoc      | 1344 +++++++++++++
 .../org/apache/camel/catalog/docs/process-eip.adoc |  155 ++
 .../apache/camel/catalog/docs/process-manager.adoc |   31 +
 .../camel/catalog/docs/properties-component.adoc   |  147 ++
 .../camel/catalog/docs/protobuf-dataformat.adoc    |  252 +++
 .../catalog/docs/protobufJackson2-dataformat.adoc  |  100 +
 .../catalog/docs/protobufJackson3-dataformat.adoc  |  100 +
 .../catalog/docs/publish-subscribe-channel.adoc    |   89 +
 .../camel/catalog/docs/pubnub-component.adoc       |  290 +++
 .../camel/catalog/docs/pulsar-component.adoc       |   38 +
 .../apache/camel/catalog/docs/python-language.adoc |   58 +
 .../camel/catalog/docs/qdrant-component.adoc       |  169 ++
 .../camel/catalog/docs/quartz-component.adoc       |  506 +++++
 .../camel/catalog/docs/quickfix-component.adoc     |  452 +++++
 .../camel/catalog/docs/randomLoadBalancer-eip.adoc |   77 +
 .../catalog/docs/reactive-executor-tomcat.adoc     |   23 +
 .../catalog/docs/reactive-executor-vertx.adoc      |   37 +
 .../catalog/docs/reactive-streams-component.adoc   |  591 ++++++
 .../org/apache/camel/catalog/docs/reactor.adoc     |   23 +
 .../camel/catalog/docs/recipientList-eip.adoc      |  526 +++++
 .../org/apache/camel/catalog/docs/redis.adoc       |   12 +
 .../apache/camel/catalog/docs/ref-component.adoc   |  114 ++
 .../apache/camel/catalog/docs/ref-language.adoc    |   78 +
 .../camel/catalog/docs/removeHeader-eip.adoc       |   71 +
 .../camel/catalog/docs/removeHeaders-eip.adoc      |  135 ++
 .../camel/catalog/docs/removeProperties-eip.adoc   |  126 ++
 .../camel/catalog/docs/removeProperty-eip.adoc     |   71 +
 .../camel/catalog/docs/removeVariable-eip.adoc     |   64 +
 .../camel/catalog/docs/requestReply-eip.adoc       |  193 ++
 .../apache/camel/catalog/docs/resequence-eip.adoc  |  688 +++++++
 .../camel/catalog/docs/resilience4j-eip.adoc       |  256 +++
 .../catalog/docs/resilience4j-micrometer.adoc      |   46 +
 .../apache/camel/catalog/docs/resilience4j.adoc    |   27 +
 .../docs/resilience4jConfiguration-eip.adoc        |   22 +
 .../catalog/docs/resourceresolver-github.adoc      |   62 +
 .../camel/catalog/docs/rest-api-component.adoc     |   22 +
 .../apache/camel/catalog/docs/rest-component.adoc  |  372 ++++
 .../camel/catalog/docs/rest-openapi-component.adoc |  278 +++
 .../camel/catalog/docs/resume-strategies.adoc      |  238 +++
 .../apache/camel/catalog/docs/return-address.adoc  |   99 +
 .../catalog/docs/robotframework-component.adoc     |  167 ++
 .../camel/catalog/docs/rocketmq-component.adoc     |  188 ++
 .../apache/camel/catalog/docs/rollback-eip.adoc    |  151 ++
 .../catalog/docs/roundRobinLoadBalancer-eip.adoc   |   78 +
 .../apache/camel/catalog/docs/routingSlip-eip.adoc |  148 ++
 .../apache/camel/catalog/docs/rss-component.adoc   |  225 +++
 .../apache/camel/catalog/docs/rss-dataformat.adoc  |  138 ++
 .../org/apache/camel/catalog/docs/rxjava.adoc      |   27 +
 .../apache/camel/catalog/docs/saga-component.adoc  |   32 +
 .../org/apache/camel/catalog/docs/saga-eip.adoc    |  946 +++++++++
 .../camel/catalog/docs/salesforce-bulk-api.adoc    |  584 ++++++
 .../camel/catalog/docs/salesforce-component.adoc   |  409 ++++
 .../camel/catalog/docs/salesforce-reports.adoc     |  117 ++
 .../camel/catalog/docs/salesforce-rest-api.adoc    | 1075 ++++++++++
 .../camel/catalog/docs/salesforce-streaming.adoc   |  381 ++++
 .../org/apache/camel/catalog/docs/sample-eip.adoc  |  214 ++
 .../catalog/docs/sap-netweaver-component.adoc      |  169 ++
 .../apache/camel/catalog/docs/scatter-gather.adoc  |  273 +++
 .../camel/catalog/docs/scheduler-component.adoc    |  132 ++
 .../camel/catalog/docs/schematron-component.adoc   |  244 +++
 .../apache/camel/catalog/docs/scp-component.adoc   |   70 +
 .../org/apache/camel/catalog/docs/script-eip.adoc  |  144 ++
 .../apache/camel/catalog/docs/seda-component.adoc  |  353 ++++
 .../camel/catalog/docs/selective-consumer.adoc     |  111 ++
 .../camel/catalog/docs/service-activator.adoc      |   59 +
 .../camel/catalog/docs/servicenow-component.adoc   |  156 ++
 .../camel/catalog/docs/servlet-component.adoc      |  356 ++++
 .../org/apache/camel/catalog/docs/setBody-eip.adoc |   94 +
 .../apache/camel/catalog/docs/setHeader-eip.adoc   |  174 ++
 .../apache/camel/catalog/docs/setHeaders-eip.adoc  |  215 ++
 .../apache/camel/catalog/docs/setProperty-eip.adoc |  167 ++
 .../apache/camel/catalog/docs/setVariable-eip.adoc |  162 ++
 .../camel/catalog/docs/setVariables-eip.adoc       |  215 ++
 .../apache/camel/catalog/docs/sftp-component.adoc  |  316 +++
 .../apache/camel/catalog/docs/shell-component.adoc |  148 ++
 .../org/apache/camel/catalog/docs/shiro.adoc       |  297 +++
 .../apache/camel/catalog/docs/simple-advanced.adoc | 1009 ++++++++++
 .../camel/catalog/docs/simple-functions.adoc       | 1169 +++++++++++
 .../apache/camel/catalog/docs/simple-language.adoc |  131 ++
 .../org/apache/camel/catalog/docs/simple-ognl.adoc |  183 ++
 .../camel/catalog/docs/simple-operators.adoc       |  371 ++++
 .../apache/camel/catalog/docs/sjms-component.adoc  |  314 +++
 .../apache/camel/catalog/docs/sjms2-component.adoc |  318 +++
 .../apache/camel/catalog/docs/slack-component.adoc |  226 +++
 .../apache/camel/catalog/docs/smb-component.adoc   |  125 ++
 .../camel/catalog/docs/smooks-component.adoc       |  151 ++
 .../camel/catalog/docs/smooks-dataformat.adoc      |   81 +
 .../apache/camel/catalog/docs/smpp-component.adoc  |  334 ++++
 .../camel/catalog/docs/snakeYaml-dataformat.adoc   |  208 ++
 .../apache/camel/catalog/docs/snmp-component.adoc  |  171 ++
 .../apache/camel/catalog/docs/soap-dataformat.adoc |  272 +++
 .../apache/camel/catalog/docs/solr-component.adoc  |  187 ++
 .../org/apache/camel/catalog/docs/sort-eip.adoc    |  184 ++
 .../apache/camel/catalog/docs/spel-language.adoc   |  168 ++
 .../org/apache/camel/catalog/docs/split-eip.adoc   | 1638 ++++++++++++++++
 .../camel/catalog/docs/splunk-component.adoc       |  325 ++++
 .../camel/catalog/docs/splunk-hec-component.adoc   |  139 ++
 .../catalog/docs/spring-ai-chat-component.adoc     | 1391 +++++++++++++
 .../docs/spring-ai-embeddings-component.adoc       |  155 ++
 .../catalog/docs/spring-ai-image-component.adoc    |  267 +++
 .../catalog/docs/spring-ai-tools-component.adoc    |  297 +++
 .../docs/spring-ai-vector-store-component.adoc     |  295 +++
 .../camel/catalog/docs/spring-batch-component.adoc |  299 +++
 .../camel/catalog/docs/spring-cloud-config.adoc    |  131 ++
 .../camel/catalog/docs/spring-event-component.adoc |   42 +
 .../camel/catalog/docs/spring-jdbc-component.adoc  |   42 +
 .../camel/catalog/docs/spring-ldap-component.adoc  |  114 ++
 .../org/apache/camel/catalog/docs/spring-main.adoc |   12 +
 .../catalog/docs/spring-rabbitmq-component.adoc    |  361 ++++
 .../camel/catalog/docs/spring-redis-component.adoc |  341 ++++
 .../apache/camel/catalog/docs/spring-security.adoc |  279 +++
 .../apache/camel/catalog/docs/spring-summary.adoc  |  503 +++++
 .../camel/catalog/docs/spring-ws-component.adoc    |  702 +++++++
 .../org/apache/camel/catalog/docs/spring-xml.adoc  |   25 +
 .../org/apache/camel/catalog/docs/springdoc.adoc   |   17 +
 .../apache/camel/catalog/docs/sql-component.adoc   | 1083 +++++++++++
 .../camel/catalog/docs/sql-stored-component.adoc   |  234 +++
 .../apache/camel/catalog/docs/ssh-component.adoc   |  193 ++
 .../apache/camel/catalog/docs/stax-component.adoc  |  212 ++
 .../org/apache/camel/catalog/docs/step-eip.adoc    |  171 ++
 .../camel/catalog/docs/stickyLoadBalancer-eip.adoc |   84 +
 .../camel/catalog/docs/stitch-component.adoc       |  240 +++
 .../org/apache/camel/catalog/docs/stop-eip.adoc    |  110 ++
 .../camel/catalog/docs/stream-component.adoc       |  235 +++
 .../camel/catalog/docs/streamConfig-eip.adoc       |   18 +
 .../catalog/docs/string-template-component.adoc    |  167 ++
 .../camel/catalog/docs/stripe-component.adoc       |  748 +++++++
 .../apache/camel/catalog/docs/stub-component.adoc  |   56 +
 .../camel/catalog/docs/swiftMt-dataformat.adoc     |  218 +++
 .../camel/catalog/docs/swiftMx-dataformat.adoc     |  218 +++
 .../camel/catalog/docs/syslog-dataformat.adoc      |  216 +++
 .../camel/catalog/docs/tahu-edge-component.adoc    |  108 ++
 .../camel/catalog/docs/tahu-host-component.adoc    |   34 +
 .../apache/camel/catalog/docs/tahu-summary.adoc    |  139 ++
 .../camel/catalog/docs/tarFile-dataformat.adoc     |  281 +++
 .../camel/catalog/docs/telegram-component.adoc     |  499 +++++
 .../apache/camel/catalog/docs/telemetry-dev.adoc   |   79 +
 .../org/apache/camel/catalog/docs/telemetry.adoc   |  166 ++
 .../catalog/docs/tensorflow-serving-component.adoc |  439 +++++
 .../org/apache/camel/catalog/docs/test-junit5.adoc |  150 ++
 .../org/apache/camel/catalog/docs/test-junit6.adoc |   76 +
 .../camel/catalog/docs/test-main-junit5.adoc       |  762 ++++++++
 .../camel/catalog/docs/test-main-junit6.adoc       |  762 ++++++++
 .../camel/catalog/docs/test-spring-junit5.adoc     |  250 +++
 .../camel/catalog/docs/test-spring-junit6.adoc     |  250 +++
 .../catalog/docs/threadpoolfactory-vertx.adoc      |   68 +
 .../org/apache/camel/catalog/docs/threads-eip.adoc |  187 ++
 .../camel/catalog/docs/thrift-component.adoc       |  153 ++
 .../camel/catalog/docs/thrift-dataformat.adoc      |  212 ++
 .../apache/camel/catalog/docs/throttle-eip.adoc    |  407 ++++
 .../camel/catalog/docs/throwException-eip.adoc     |  111 ++
 .../camel/catalog/docs/thymeleaf-component.adoc    |  430 ++++
 .../apache/camel/catalog/docs/tika-component.adoc  |  116 ++
 .../apache/camel/catalog/docs/timer-component.adoc |  204 ++
 .../org/apache/camel/catalog/docs/to-eip.adoc      |  252 +++
 .../org/apache/camel/catalog/docs/toD-eip.adoc     |  419 ++++
 .../camel/catalog/docs/tokenize-language.adoc      |   89 +
 .../camel/catalog/docs/topicLoadBalancer-eip.adoc  |   78 +
 .../org/apache/camel/catalog/docs/tracing.adoc     |  133 ++
 .../camel/catalog/docs/transactional-client.adoc   |  532 +++++
 .../apache/camel/catalog/docs/transform-eip.adoc   |   98 +
 .../camel/catalog/docs/transformDataType-eip.adoc  |   88 +
 .../camel/catalog/docs/twilio-component.adoc       |   75 +
 .../docs/twitter-directmessage-component.adoc      |   29 +
 .../catalog/docs/twitter-search-component.adoc     |   21 +
 .../catalog/docs/twitter-timeline-component.adoc   |   29 +
 .../camel/catalog/docs/undertow-component.adoc     |  458 +++++
 .../catalog/docs/undertow-spring-security.adoc     |   31 +
 .../catalog/docs/univocityCsv-dataformat.adoc      |  298 +++
 .../catalog/docs/univocityFixed-dataformat.adoc    |  293 +++
 .../catalog/docs/univocityTsv-dataformat.adoc      |  293 +++
 .../apache/camel/catalog/docs/unmarshal-eip.adoc   |  126 ++
 .../apache/camel/catalog/docs/validate-eip.adoc    |  127 ++
 .../camel/catalog/docs/validator-component.adoc    |   58 +
 .../camel/catalog/docs/variable-language.adoc      |   67 +
 .../camel/catalog/docs/velocity-component.adoc     |  433 +++++
 .../apache/camel/catalog/docs/vertx-component.adoc |   60 +
 .../camel/catalog/docs/vertx-http-component.adoc   |  201 ++
 .../catalog/docs/vertx-websocket-component.adoc    |  343 ++++
 .../org/apache/camel/catalog/docs/wal.adoc         |   47 +
 .../apache/camel/catalog/docs/wasm-component.adoc  |  192 ++
 .../apache/camel/catalog/docs/wasm-language.adoc   |  153 ++
 .../camel/catalog/docs/weather-component.adoc      |  195 ++
 .../camel/catalog/docs/weaviate-component.adoc     |   34 +
 .../apache/camel/catalog/docs/web3j-component.adoc |  173 ++
 .../camel/catalog/docs/webhook-component.adoc      |   55 +
 .../catalog/docs/weightedLoadBalancer-eip.adoc     |   80 +
 .../camel/catalog/docs/whatsapp-component.adoc     |  112 ++
 .../org/apache/camel/catalog/docs/wireTap-eip.adoc |  177 ++
 .../camel/catalog/docs/wordpress-component.adoc    |   93 +
 .../camel/catalog/docs/workday-component.adoc      |   38 +
 .../camel/catalog/docs/xchange-component.adoc      |  106 +
 .../apache/camel/catalog/docs/xj-component.adoc    |  551 ++++++
 .../camel/catalog/docs/xmlSecurity-dataformat.adoc |  318 +++
 .../catalog/docs/xmlsecurity-sign-component.adoc   |  656 +++++++
 .../catalog/docs/xmlsecurity-verify-component.adoc |  604 ++++++
 .../apache/camel/catalog/docs/xmpp-component.adoc  |  277 +++
 .../apache/camel/catalog/docs/xpath-language.adoc  |  840 ++++++++
 .../camel/catalog/docs/xquery-component.adoc       |  263 +++
 .../apache/camel/catalog/docs/xquery-language.adoc |  303 +++
 .../apache/camel/catalog/docs/xslt-component.adoc  |  406 ++++
 .../camel/catalog/docs/xslt-saxon-component.adoc   |  514 +++++
 .../camel/catalog/docs/xtokenize-language.adoc     |   28 +
 .../org/apache/camel/catalog/docs/yaml-dsl.adoc    |  888 +++++++++
 .../apache/camel/catalog/docs/zeebe-component.adoc |  356 ++++
 .../camel/catalog/docs/zendesk-component.adoc      |   45 +
 .../camel/catalog/docs/zipDeflater-dataformat.adoc |  108 ++
 .../camel/catalog/docs/zipFile-dataformat.adoc     |  273 +++
 .../camel/catalog/docs/zookeeper-component.adoc    |  340 ++++
 .../catalog/docs/zookeeper-master-component.adoc   |  167 ++
 .../org/apache/camel/catalog/CamelCatalog.java     |   58 +
 .../apache/camel/catalog/DefaultCamelCatalog.java  |   45 +
 .../org/apache/camel/catalog/CamelCatalogTest.java |   60 +
 .../modules/ROOT/pages/camel-catalog.adoc          |   40 +
 .../camel/maven/packaging/PrepareCatalogMojo.java  |   59 +
 699 files changed, 193346 insertions(+)

diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs.properties b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs.properties
new file mode 100644
index 000000000000..518dd4f70586
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs.properties
@@ -0,0 +1,693 @@
+a2a-component
+a2a-consumer
+a2a-producer
+activemq-component
+activemq6-component
+aggregate-eip
+ai-patterns
+ai-tool-component
+amqp-component
+arangodb-component
+as2-component
+asn1-dataformat
+asterisk-component
+atmosphere-websocket-component
+atom-component
+attachments
+avro-component
+avro-dataformat
+avroJackson2-dataformat
+avroJackson3-dataformat
+aws-bedrock-agent-component
+aws-bedrock-agent-runtime-component
+aws-bedrock-component
+aws-bedrock-examples
+aws-bedrock-models
+aws-cloudtrail-component
+aws-config-component
+aws-secrets-manager-component
+aws-security-hub-component
+aws2-athena-component
+aws2-comprehend-component
+aws2-cw-component
+aws2-ddb-component
+aws2-ddbstream-component
+aws2-ec2-component
+aws2-ecs-component
+aws2-eks-component
+aws2-eventbridge-component
+aws2-iam-component
+aws2-kinesis-component
+aws2-kinesis-firehose-component
+aws2-kms-component
+aws2-lambda-component
+aws2-mq-component
+aws2-msk-component
+aws2-polly-component
+aws2-redshift-data-component
+aws2-rekognition-component
+aws2-s3-component
+aws2-s3-consumer-examples
+aws2-s3-producer-operations
+aws2-s3-streaming
+aws2-s3-vectors-component
+aws2-ses-component
+aws2-sns-component
+aws2-sqs-component
+aws2-step-functions-component
+aws2-sts-component
+aws2-textract-component
+aws2-timestream-component
+aws2-transcribe-component
+aws2-translate-component
+azure-cosmosdb-component
+azure-eventhubs-component
+azure-files-component
+azure-functions-component
+azure-key-vault-component
+azure-schema-registry
+azure-servicebus-component
+azure-storage-blob-component
+azure-storage-blob-consumer
+azure-storage-blob-operations
+azure-storage-datalake-component
+azure-storage-queue-component
+barcode-dataformat
+base64-dataformat
+batchConfig-eip
+bean-component
+bean-eip
+bean-language
+bean-validator-component
+beanio-dataformat
+bindy-dataformat
+bonita-component
+box-component
+braintree-component
+browse-component
+caffeine-cache-component
+caffeine-loadcache-component
+camunda-component
+cbor-dataformat
+change-data-capture
+channel-adapter
+chatscript-component
+choice-eip
+chunk-component
+circuitBreaker-eip
+claimCheck-eip
+class-component
+cli-connector
+cli-debug
+clickup-component
+cloudevents
+cm-sms-component
+coap-component
+cometd-component
+competing-consumers
+composed-message-processor
+constant-language
+consul-component
+content-enricher
+content-filter-eip
+controlbus-component
+convertBodyTo-eip
+convertHeaderTo-eip
+convertVariableTo-eip
+correlation-identifier
+couchbase-component
+couchdb-component
+cql-component
+cron-component
+crypto-component
+crypto-dataformat
+csimple-joor
+csimple-language
+csv-dataformat
+customLoadBalancer-eip
+cxf-component
+cxfrs-component
+cyberark-vault-component
+dapr-component
+dataformat-component
+dataset-component
+dataset-test-component
+datasonnet-language
+dead-letter-channel
+debezium-db2-component
+debezium-mongodb-component
+debezium-mysql-component
+debezium-oracle-component
+debezium-postgres-component
+debezium-sqlserver-component
+debug
+delay-eip
+dfdl-component
+dfdl-dataformat
+dhis2-component
+diagram
+digitalocean-component
+direct-component
+disruptor-component
+disruptor-vm-component
+djl-component
+dns-component
+docker-component
+docling-async-processing
+docling-batch-processing
+docling-component
+docling-serve
+drill-component
+dropbox-component
+dsl-modeline
+durable-subscriber
+dynamic-router-component
+dynamic-router-control-component
+dynamicRouter-eip
+ehcache-component
+eip-exchangeProperties
+eip-options
+elasticsearch-component
+elasticsearch-rest-client-component
+enrich-eip
+enterprise-integration-patterns
+event-component
+event-message
+eventDrivenConsumer-eip
+exchangeProperty-language
+exec-component
+failoverLoadBalancer-eip
+fastjson-dataformat
+fault-tolerance-eip
+faultToleranceConfiguration-eip
+fhir-component
+fhirJson-dataformat
+fhirXml-dataformat
+file-component
+file-language
+file-watch-component
+filter-eip
+flatpack-component
+flatpack-dataformat
+flink-component
+flowable-component
+fop-component
+fory-dataformat
+freemarker-component
+from-eip
+ftp-component
+ftps-component
+geocoder-component
+git-component
+github2-component
+google-bigquery-component
+google-bigquery-sql-component
+google-calendar-component
+google-calendar-stream-component
+google-drive-component
+google-firestore-component
+google-functions-component
+google-mail-component
+google-mail-stream-component
+google-pubsub-component
+google-secret-manager-component
+google-sheets-component
+google-sheets-stream-component
+google-speech-to-text-component
+google-storage-component
+google-text-to-speech-component
+google-vertexai-component
+google-vision-component
+graphql-component
+grok-dataformat
+groovy-language
+groovyJson-dataformat
+groovyXml-dataformat
+grpc-component
+gson-dataformat
+guaranteed-delivery
+gzipDeflater-dataformat
+hashicorp-vault-component
+hazelcast-atomicvalue-component
+hazelcast-instance-component
+hazelcast-list-component
+hazelcast-map-component
+hazelcast-multimap-component
+hazelcast-pncounter-component
+hazelcast-queue-component
+hazelcast-replicatedmap-component
+hazelcast-ringbuffer-component
+hazelcast-seda-component
+hazelcast-set-component
+hazelcast-summary
+hazelcast-topic-component
+header-language
+headersmap
+hl7-dataformat
+hl7terser-language
+http-component
+huggingface-component
+hwcloud-dms-component
+hwcloud-frs-component
+hwcloud-functiongraph-component
+hwcloud-iam-component
+hwcloud-imagerecognition-component
+hwcloud-obs-component
+hwcloud-smn-component
+ibm-cos-component
+ibm-secrets-manager-component
+ibm-watson-discovery-component
+ibm-watson-language-component
+ibm-watson-speech-to-text-component
+ibm-watson-text-to-speech-component
+ibm-watsonx-ai-component
+ibm-watsonx-ai-examples
+ibm-watsonx-data-component
+ical-dataformat
+idempotentConsumer-eip
+iec60870-client-component
+iec60870-server-component
+iggy-component
+ignite-cache-component
+ignite-compute-component
+ignite-events-component
+ignite-idgen-component
+ignite-messaging-component
+ignite-queue-component
+ignite-set-component
+ignite-summary
+infinispan-component
+infinispan-embedded-component
+influxdb-component
+influxdb2-component
+intercept
+irc-component
+ironmq-component
+iso8583-dataformat
+jackson2-dataformat
+jackson3-dataformat
+jacksonXml2-dataformat
+jacksonXml3-dataformat
+jandex
+jasypt
+java-joor-dsl
+java-language
+java-xml-io-dsl
+java-xml-jaxb-dsl
+jaxb-dataformat
+jcache-component
+jcr-component
+jdbc-component
+jetty-component
+jfr
+jgroups-component
+jgroups-raft-component
+jira-component
+jms-component
+jmx-component
+jolt-component
+jooq-component
+joor-language
+jpa-component
+jq-language
+js-language
+jslt-component
+json-patch-component
+json-validator-component
+jsonApi-dataformat
+jsonata-component
+jsonb-dataformat
+jsonpath-language
+jsoup
+jt400-component
+jta
+jte-component
+kafka-component
+kamelet-component
+kamelet-eip
+kamelet-main
+kamelet-main-support
+keycloak-component
+keycloak-consumer
+keycloak-producer
+keycloak-security
+knative-component
+kserve-component
+kubernetes-config-maps-component
+kubernetes-cronjob-component
+kubernetes-custom-resources-component
+kubernetes-deployments-component
+kubernetes-events-component
+kubernetes-hpa-component
+kubernetes-job-component
+kubernetes-namespaces-component
+kubernetes-nodes-component
+kubernetes-persistent-volumes-claims-component
+kubernetes-persistent-volumes-component
+kubernetes-pods-component
+kubernetes-replication-controllers-component
+kubernetes-resources-quota-component
+kubernetes-secrets-component
+kubernetes-service-accounts-component
+kubernetes-services-component
+kubernetes-summary
+kudu-component
+langchain4j-agent-component
+langchain4j-agent-guardrails
+langchain4j-agent-mcp
+langchain4j-agent-multimodal
+langchain4j-chat-component
+langchain4j-embeddings-component
+langchain4j-embeddingstore-component
+langchain4j-tokenizer
+langchain4j-tools-component
+langchain4j-web-search-component
+language-component
+ldap-component
+ldif-component
+leveldb
+loadBalance-eip
+log-component
+log-eip
+loop-eip
+lpr-component
+lra
+lucene-component
+lumberjack-component
+lzf-dataformat
+mail-component
+mail-microsoft-oauth
+main
+mapstruct-component
+marshal-eip
+master-component
+mdc
+message
+message-broker
+message-bus
+message-channel
+message-dispatcher
+message-endpoint
+message-expiration
+message-history
+message-router
+message-translator
+messaging-bridge
+messaging-gateway
+messaging-mapper
+metrics-component
+micrometer-component
+micrometer-observability
+micrometer-prometheus
+microprofile-config
+microprofile-fault-tolerance
+microprofile-health
+milo-browse-component
+milo-client-component
+milo-server-component
+milvus-component
+mimeMultipart-dataformat
+mina-component
+mina-sftp-authentication
+mina-sftp-component
+mina-sftp-migration
+mina-sftp-security
+minio-component
+mllp-component
+mock-component
+mongodb-component
+mongodb-gridfs-component
+multicast-eip
+mustache-component
+mvel-component
+mvel-language
+mybatis-bean-component
+mybatis-component
+nats-component
+neo4j-component
+netty-component
+netty-http-component
+normalizer
+oaipmh-component
+oauth
+observability-services
+observation
+ocsf-dataformat
+ognl-language
+olingo2-component
+olingo4-component
+onFallback-eip
+once-component
+openai-component
+openai-mcp
+openai-operations
+openai-providers
+openapi-java
+openapi-validator
+opensearch-component
+openshift-build-configs-component
+openshift-builds-component
+openshift-deploymentconfigs-component
+openstack-cinder-component
+openstack-glance-component
+openstack-keystone-component
+openstack-neutron-component
+openstack-nova-component
+openstack-summary
+openstack-swift-component
+opentelemetry
+opentelemetry-metrics-component
+opentelemetry2
+optaplanner-component
+paho-component
+paho-mqtt5-component
+parquetAvro-dataformat
+pdf-component
+pg-replication-slot-component
+pgevent-component
+pgp-dataformat
+pgvector-component
+pinecone-component
+pipeline-eip
+platform-http-component
+platform-http-jolokia
+platform-http-main
+platform-http-vertx
+plc4x-component
+point-to-point-channel
+poll-eip
+pollEnrich-eip
+polling-consumer
+pqc-component
+pqc-dataformat
+pqc-hybrid
+pqc-key-lifecycle
+process-eip
+process-manager
+properties-component
+protobuf-dataformat
+protobufJackson2-dataformat
+protobufJackson3-dataformat
+publish-subscribe-channel
+pubnub-component
+pulsar-component
+python-language
+qdrant-component
+quartz-component
+quickfix-component
+randomLoadBalancer-eip
+reactive-executor-tomcat
+reactive-executor-vertx
+reactive-streams-component
+reactor
+recipientList-eip
+redis
+ref-component
+ref-language
+removeHeader-eip
+removeHeaders-eip
+removeProperties-eip
+removeProperty-eip
+removeVariable-eip
+requestReply-eip
+resequence-eip
+resilience4j
+resilience4j-eip
+resilience4j-micrometer
+resilience4jConfiguration-eip
+resourceresolver-github
+rest-api-component
+rest-component
+rest-openapi-component
+resume-strategies
+return-address
+robotframework-component
+rocketmq-component
+rollback-eip
+roundRobinLoadBalancer-eip
+routingSlip-eip
+rss-component
+rss-dataformat
+rxjava
+saga-component
+saga-eip
+salesforce-bulk-api
+salesforce-component
+salesforce-reports
+salesforce-rest-api
+salesforce-streaming
+sample-eip
+sap-netweaver-component
+scatter-gather
+scheduler-component
+schematron-component
+scp-component
+script-eip
+seda-component
+selective-consumer
+service-activator
+servicenow-component
+servlet-component
+setBody-eip
+setHeader-eip
+setHeaders-eip
+setProperty-eip
+setVariable-eip
+setVariables-eip
+sftp-component
+shell-component
+shiro
+simple-advanced
+simple-functions
+simple-language
+simple-ognl
+simple-operators
+sjms-component
+sjms2-component
+slack-component
+smb-component
+smooks-component
+smooks-dataformat
+smpp-component
+snakeYaml-dataformat
+snmp-component
+soap-dataformat
+solr-component
+sort-eip
+spel-language
+split-eip
+splunk-component
+splunk-hec-component
+spring-ai-chat-component
+spring-ai-embeddings-component
+spring-ai-image-component
+spring-ai-tools-component
+spring-ai-vector-store-component
+spring-batch-component
+spring-cloud-config
+spring-event-component
+spring-jdbc-component
+spring-ldap-component
+spring-main
+spring-rabbitmq-component
+spring-redis-component
+spring-security
+spring-summary
+spring-ws-component
+spring-xml
+springdoc
+sql-component
+sql-stored-component
+ssh-component
+stax-component
+step-eip
+stickyLoadBalancer-eip
+stitch-component
+stop-eip
+stream-component
+streamConfig-eip
+string-template-component
+stripe-component
+stub-component
+swiftMt-dataformat
+swiftMx-dataformat
+syslog-dataformat
+tahu-edge-component
+tahu-host-component
+tahu-summary
+tarFile-dataformat
+telegram-component
+telemetry
+telemetry-dev
+tensorflow-serving-component
+test-junit5
+test-junit6
+test-main-junit5
+test-main-junit6
+test-spring-junit5
+test-spring-junit6
+threadpoolfactory-vertx
+threads-eip
+thrift-component
+thrift-dataformat
+throttle-eip
+throwException-eip
+thymeleaf-component
+tika-component
+timer-component
+to-eip
+toD-eip
+tokenize-language
+topicLoadBalancer-eip
+tracing
+transactional-client
+transform-eip
+transformDataType-eip
+twilio-component
+twitter-directmessage-component
+twitter-search-component
+twitter-timeline-component
+undertow-component
+undertow-spring-security
+univocityCsv-dataformat
+univocityFixed-dataformat
+univocityTsv-dataformat
+unmarshal-eip
+validate-eip
+validator-component
+variable-language
+velocity-component
+vertx-component
+vertx-http-component
+vertx-websocket-component
+wal
+wasm-component
+wasm-language
+weather-component
+weaviate-component
+web3j-component
+webhook-component
+weightedLoadBalancer-eip
+whatsapp-component
+wireTap-eip
+wordpress-component
+workday-component
+xchange-component
+xj-component
+xmlSecurity-dataformat
+xmlsecurity-sign-component
+xmlsecurity-verify-component
+xmpp-component
+xpath-language
+xquery-component
+xquery-language
+xslt-component
+xslt-saxon-component
+xtokenize-language
+yaml-dsl
+zeebe-component
+zendesk-component
+zipDeflater-dataformat
+zipFile-dataformat
+zookeeper-component
+zookeeper-master-component
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/a2a-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/a2a-component.adoc
new file mode 100644
index 000000000000..83df5aa1b0f5
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/a2a-component.adoc
@@ -0,0 +1,766 @@
+= A2A Component
+:doctitle: A2A
+:shortname: a2a
+:artifactid: camel-a2a
+:description: A2A endpoint for agent-to-agent communication.
+:since: 4.21
+:supportlevel: Preview
+:tabs-sync-option:
+:component-header: Both producer and consumer are supported
+//Manually maintained attributes
+:group: AI
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The A2A component implements the https://a2a-protocol.org/latest/specification/[Agent-to-Agent (A2A) v1.0 protocol], enabling Camel routes to both expose and call A2A-compliant agents.
+
+As a *consumer*, it turns a Camel route into an A2A agent — automatically serving an agent card at `/.well-known/agent-card.json`, exposing all A2A operations via HTTP, and managing task state. As a *producer*, it calls remote A2A agents with automatic agent card discovery, protocol wrapping, and credential management.
+
+The component follows the same design philosophy as xref:rest-openapi-component.adoc[REST OpenAPI]: it handles protocol plumbing and delegates business logic entirely to the route.
+
+[NOTE]
+====
+*A2A Protocol*
+
+The https://a2a-protocol.org[A2A protocol] is an open standard for communication between AI agents. It defines how agents discover each other (via agent cards), exchange messages, manage long-running tasks, stream progress updates, and deliver push notifications. The protocol supports both REST (HTTP+JSON) and JSON-RPC 2.0 bindings over HTTP.
+====
+
+== Preview Limitations
+
+The A2A component is Preview in Camel {since}. It targets the A2A v1.0 protocol, but endpoint options, model classes, generated metadata, and the task-store SPI may still change before the component reaches stable support.
+
+Current Preview limitations:
+
+* Extended Agent Card / `GetExtendedAgentCard` is not implemented in this first release.
+* Consumers validate operation requests by default. Local-only examples in this page set `validateAuth=false`; network-exposed agents should use an agent card with `securitySchemes` and `securityRequirements` plus `apiKey`, `bearerToken`, or `oauthProfile` endpoint configuration.
+* The REST binding uses A2A custom-method paths containing colons, such as `/message:send`. These paths collide on Vert.x/platform-http. Use `protocolBinding=JSONRPC` with platform-http, or use `httpServerComponent=undertow` or `httpServerComponent=jetty` for REST custom-method routes.
+* Real-time SSE streaming is verified with Vert.x/platform-http, Undertow, and Jetty.
+* The default task store is in-memory and single-JVM. Register a custom `A2ATaskStore` for durable or cross-node task state.
+
+Maven users will need to add the following dependency to their `pom.xml`:
+
+[source,xml]
+----
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-a2a</artifactId>
+    <version>x.x.x</version>
+    <!-- use the same version as your Camel core version -->
+</dependency>
+----
+
+Consumer routes also need an HTTP server component at runtime. For example, add `camel-platform-http-vertx` for JSON-RPC agents (including SSE streaming), or `camel-undertow` / `camel-jetty` for REST custom-method routes. See <<Dependencies>> and <<HTTP Server Component Discovery>>.
+
+== URI Format
+
+----
+a2a:agentCardSource[?options]
+----
+
+How *agentCardSource* determines where the agent card is loaded from:
+
+[cols="1,3"]
+|===
+| Source | Example
+
+| Remote URL (partial)
+| `a2a:\https://agent.example.com` — auto-expands to `+https://agent.example.com/.well-known/agent-card.json+`
+
+| Remote URL (full)
+| `a2a:\https://agent.example.com/.well-known/agent-card.json`
+
+| Classpath
+| `a2a:classpath:cards/weather.json`
+
+| File
+| `a2a:file:/etc/agents/weather.json`
+
+| Plain name
+| `a2a:weather-agent?name=Weather&description=...` — card built from params
+|===
+
+The same URI works in both `from()` (consumer: "I am this agent") and `to()` (producer: "I am calling this agent").
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+== Sub-Pages
+
+For more details on consumer and producer usage, see:
+
+* xref:others:a2a-consumer.adoc[Consumer Guide] - Exposing an A2A agent with authentication, SSE streaming, async tasks, push notifications, and capacity limiting
+* xref:others:a2a-producer.adoc[Producer Guide] - Calling remote agents with streaming, async task lifecycle, push notifications, and parallel multicast
+
+== Simple Language Functions
+
+The component registers custom Simple language functions under the `a2a:` namespace:
+
+[cols="2,3"]
+|===
+| Function | Description
+
+| `${a2a:emit('message')}`
+| Emit a status update with `WORKING` state. Used in `script` EIP for SSE streaming side effects.
+
+| `${a2a:emit(STATE, 'message')}`
+| Emit a status update with an explicit `TaskState` (e.g., `INPUT_REQUIRED`).
+
+| `${a2a:text}`
+| Extract `TextPart` content from the body (`Task` or `Message`). If the body is a `Task`, extracts from the last history message.
+
+| `${a2a:text(expression)}`
+| Extract `TextPart` content from the result of a Simple expression.
+
+| `${a2a:data}`
+| Extract `DataPart` content as a JSON string from the body.
+
+| `${a2a:data(expression)}`
+| Extract `DataPart` content from the result of a Simple expression.
+
+| `${a2a:file}`
+| Extract `FilePart` content — the `url` value for URL file parts, or a binary-size description for inline base64 `raw` content.
+
+| `${a2a:file(expression)}`
+| Extract `FilePart` content from the result of a Simple expression.
+
+| `${a2a:card}`
+| Full agent card as JSON string. Resolves the card from the A2A endpoint (consumer's own card, or the cached remote card on the producer).
+
+| `${a2a:card.name}`
+| Agent card name.
+
+| `${a2a:card.description}`
+| Agent card description.
+
+| `${a2a:card.url}`
+| Agent card URL.
+
+| `${a2a:card.version}`
+| Agent card version.
+
+| `${a2a:card.skills}`
+| Skills formatted as human-readable text, one per line: `* Skill Name: description`.
+
+| `${a2a:card.skills.json}`
+| Skills as a JSON array string.
+
+| `${a2a:card.iconUrl}`
+| Agent card icon URL.
+
+| `${a2a:card.documentationUrl}`
+| Agent card documentation URL.
+
+| `${a2a:card.provider}`
+| Agent provider as JSON string.
+
+| `${a2a:card.capabilities}`
+| Agent capabilities as JSON string.
+
+| `${a2a:card.supportedInterfaces}`
+| Supported interfaces as JSON array string.
+
+| `${a2a:card.securitySchemes}`
+| Security schemes as JSON object string.
+
+| `${a2a:card.securityRequirements}`
+| A2A v1.0 security requirements as JSON array string.
+
+| `${a2a:card.security}`
+| Legacy draft `security` field as JSON array string.
+|===
+
+The `${a2a:card}` functions resolve the agent card from the exchange context. On a consumer route, `exchange.getFromEndpoint()` provides the agent's own card. On a producer route, the component scans registered endpoints for a cached remote card. Returns an empty string if no card is available.
+
+NOTE: The card functions support flat field access only — nested property access like `${a2a:card.skills[0].name}` or `${a2a:card.provider.organization}` is not supported. For structured data, use `${a2a:card.skills.json}` or `${a2a:card}` (full JSON) and parse downstream.
+
+Example — including remote agent skills in an LLM prompt:
+
+[source,yaml]
+----
+- setBody:
+    simple: |
+      Generate a plan using these available skills:
+      ${a2a:card.skills}
+----
+
+For the full text of all parts combined, use the TypeConverter:
+
+[source,yaml]
+----
+- convertBodyTo:
+    type: String
+----
+
+== Exchange Headers
+
+[cols="2,1,3"]
+|===
+| Header | Type | Description
+
+| `CamelA2AOperation`
+| `String`
+| A2A operation to invoke. Accepts both enum names (`TASK_GET`, `PUSH_CONFIG_CREATE`) and PascalCase method names (`GetTask`, `CreateTaskPushNotificationConfig`).
+
+| `CamelA2ATaskId`
+| `String`
+| Task ID for `GetTask`, `CancelTask`, `SubscribeToTask`, and push notification operations.
+
+| `CamelA2APushConfigId`
+| `String`
+| Push notification config ID for get/delete operations.
+
+| `CamelA2AContextId`
+| `String`
+| Context ID for multi-turn conversations. Set automatically on consumer inbound and producer response.
+
+| `CamelA2AMessageId`
+| `String`
+| Message ID from the request/response.
+
+| `CamelA2ATaskState`
+| `String`
+| Task state from the response (e.g., `TASK_STATE_COMPLETED`, `TASK_STATE_WORKING`).
+
+| `CamelA2AMethod`
+| `String`
+| A2A method name invoked (set on producer response).
+
+| `CamelA2AResponseType`
+| `String`
+| Response type after a producer call (`task`, `message`, `taskList`, `pushConfigList`, or `stream`). On consumer routes, set this header to `message` to return a message-only `SendMessage` response; the default is a task response.
+
+| `CamelA2AReturnImmediately`
+| `Boolean`
+| Override `returnImmediately` per-request. Takes precedence over endpoint-level config.
+
+| `CamelA2AHistoryLength`
+| `Integer`
+| Producer request field for `GetTask` and `SubscribeToTask`.
+
+| `CamelA2AUserProfile`
+| `Map<String, Object>`
+| Authenticated user profile (set as exchange *property*, not a header). Populated when `validateAuth=true` and authentication succeeds. Access via `$\{exchangeProperty.CamelA2AUserProfile}` in Simple expressions.
+
+| `CamelA2AListContextId`
+| `String`
+| Context ID filter for `ListTasks`.
+
+| `CamelA2AListPageSize`
+| `Integer`
+| Page size for `ListTasks`.
+
+| `CamelA2AListPageToken`
+| `String`
+| Pagination token for `ListTasks`.
+
+| `CamelA2AListStatus`
+| `String`
+| Comma-separated status filter for `ListTasks`.
+
+| `CamelA2AListIncludeArtifacts`
+| `Boolean`
+| Whether `ListTasks` responses include artifacts.
+
+| `CamelA2AListHistoryLength`
+| `Integer`
+| Maximum history messages to include per task in `ListTasks` responses.
+
+| `CamelA2AListStatusTimestampAfter`
+| `String`
+| Status timestamp filter for `ListTasks`. Use an ISO-8601 offset date-time.
+
+| `CamelA2AExtensions`
+| `List<String>`
+| Consumer-side negotiated A2A extension URIs from the `A2A-Extensions` request header. Set as both an exchange property and a route header after validation.
+
+| `CamelA2AStreamEmitter`
+| `A2AStreamEmitter`
+| Consumer-side: the stream emitter injected for streaming routes. Available for advanced use cases — prefer `${a2a:emit()}` or `A2AProgress` API for most agents.
+|===
+
+NOTE: `CamelA2AResponseTask` and `CamelA2AUserProfile` are exchange *properties*, not headers. Access them via `$\{exchangeProperty.CamelA2AResponseTask}` and `$\{exchangeProperty.CamelA2AUserProfile}` in Simple expressions. `CamelA2AResponseTask` contains the full `Task` object from the producer response, useful in polling workflows. `CamelA2AUserProfile` contains the authenticated user's profile map, available when `validateAuth=true`.
+
+== Supported Operations
+
+[cols="1,1,1,1"]
+|===
+| Operation (enum) | Method Name | Producer | Consumer
+
+| `MESSAGE_SEND`
+| `SendMessage`
+| Send message, receive Task or Message
+| Route processes message
+
+| `MESSAGE_STREAM`
+| `SendStreamingMessage`
+| Lazy `Iterator<StreamResponse>` (`PAYLOAD`/`POJO`), or raw `InputStream` (`RAW`)
+| Route emits via `${a2a:emit()}`
+
+| `TASK_GET`
+| `GetTask`
+| Retrieve task from remote
+| Read from task store
+
+| `TASK_LIST`
+| `ListTasks`
+| List tasks from remote
+| Query task store
+
+| `TASK_CANCEL`
+| `CancelTask`
+| Cancel remote task
+| Update store + cancel in-flight async
+
+| `TASK_SUBSCRIBE`
+| `SubscribeToTask`
+| Lazy `Iterator<StreamResponse>` of task updates
+| Event-to-Stream Bridge (real-time SSE) for REST and JSON-RPC bindings
+
+| `PUSH_CONFIG_CREATE`
+| `CreateTaskPushNotificationConfig`
+| Register webhook
+| Store config + SSRF validation
+
+| `PUSH_CONFIG_GET`
+| `GetTaskPushNotificationConfig`
+| Retrieve config
+| Read from store
+
+| `PUSH_CONFIG_LIST`
+| `ListTaskPushNotificationConfigs`
+| List configs
+| Read from store
+
+| `PUSH_CONFIG_DELETE`
+| `DeleteTaskPushNotificationConfig`
+| Delete config
+| Remove from store
+
+|===
+
+The `CamelA2AOperation` header accepts both the enum name (left column) and the PascalCase method name (second column).
+
+The built-in JSON-RPC consumer dispatches `SendMessage`, `SendStreamingMessage`, `GetTask`, `ListTasks`, `CancelTask`, `SubscribeToTask`, and the push notification config operations.
+
+== Pluggable Authentication
+
+Authentication uses a strategy-per-scheme pattern via the `A2ASecuritySchemeHandler` SPI. One handler covers both producer (apply credentials) and consumer (validate credentials) for a given security scheme type.
+
+Default handlers:
+
+[cols="1,1,2"]
+|===
+| Scheme Type | Handler | Description
+
+| `http` (bearer)
+| `HttpBearerSchemeHandler`
+| OAuth profile or static bearer token
+
+| `apiKey`
+| `ApiKeySchemeHandler`
+| API key in `header`, `query`, or `cookie` location. If the security scheme declares `location=header` and `name`, that header is used; otherwise `apiKeyHeader` is used.
+
+| `oauth2`
+| `OAuth2SchemeHandler`
+| Token via `camel-oauth` SPI
+
+| `openIdConnect`
+| `OpenIdConnectSchemeHandler`
+| Same as OAuth2, stores OIDC discovery URL
+|===
+
+Override or extend by registering a custom handler bean:
+
+._Java-only: implementing a custom A2ASecuritySchemeHandler_
+[source,java]
+----
+@BindToRegistry("myCustomAuth")
+public class MutualTlsHandler implements A2ASecuritySchemeHandler {
+    public String schemeType() { return "mutualTls"; }
+
+    public void applyCredentials(Exchange exchange, SecurityScheme scheme,
+            A2AConfiguration config, CamelContext context) {
+        // producer: configure mTLS
+    }
+
+    public A2AUserProfile validateCredentials(Exchange exchange,
+            SecurityScheme scheme, A2AConfiguration config) {
+        // consumer: extract client certificate
+        return A2AUserProfile.fromMap(Map.of(
+                "scheme", "mutualTls",
+                "subject", "CN=client"));
+    }
+}
+----
+
+=== Security Scheme Priority
+
+When the agent card declares multiple security schemes, selection is based on configuration hints:
+
+* `oauthProfile` configured → OAuth2 / OpenID Connect schemes tried first
+* `bearerToken` configured → HTTP bearer schemes tried first
+* `apiKey` configured → API key schemes tried first
+* No hint → schemes tried in agent card declaration order
+
+On the producer, the first matching handler applies credentials. On the consumer, all declared schemes are tried until one succeeds (or all fail with 401).
+
+== Task State Machine
+
+A2A tasks follow this state machine:
+
+----
+                    +--> COMPLETED
+                    |
+SUBMITTED --> WORKING +--> FAILED
+                    |
+                    +--> CANCELED
+                    |
+                    +--> INPUT_REQUIRED --> WORKING (resumed)
+                    |
+                    +--> AUTH_REQUIRED --> WORKING (after re-auth)
+                    |
+                    +--> REJECTED
+----
+
+All valid task states (wire values use the A2A v1.0 proto names shown below; the `$\{a2a:emit()}` function uses the short Java enum names — e.g., `INPUT_REQUIRED`, not `TASK_STATE_INPUT_REQUIRED`):
+
+[cols="1,3"]
+|===
+| State | Description
+
+| `TASK_STATE_UNSPECIFIED`
+| Unknown or missing task state fallback
+
+| `TASK_STATE_SUBMITTED`
+| Task accepted, not yet processing
+
+| `TASK_STATE_WORKING`
+| Task is actively being processed
+
+| `TASK_STATE_COMPLETED`
+| Task completed successfully (terminal)
+
+| `TASK_STATE_FAILED`
+| Task failed due to error or timeout (terminal)
+
+| `TASK_STATE_CANCELED`
+| Task was canceled by the client (terminal)
+
+| `TASK_STATE_INPUT_REQUIRED`
+| Agent needs additional input from the client before proceeding
+
+| `TASK_STATE_AUTH_REQUIRED`
+| Agent needs the client to re-authenticate before proceeding
+
+| `TASK_STATE_REJECTED`
+| Agent rejected the task (terminal)
+|===
+
+The consumer manages transitions automatically:
+
+* `SUBMITTED` — when `returnImmediately=true` and the task is accepted
+* `WORKING` — when the route starts processing (async tasks)
+* `COMPLETED` — when `setBody` produces a non-null response
+* `FAILED` — when the route throws an exception or `asyncTimeout` expires
+
+Routes can emit any state explicitly via `${a2a:emit(INPUT_REQUIRED, 'Please provide your address')}` or `A2AProgress.emit(exchange, TaskState.AUTH_REQUIRED, "Re-authentication needed")`.
+
+== Unified Body-as-Response
+
+Both streaming and async agents use the same route pattern — `setBody` is always the final response:
+
+[source,yaml]
+----
+steps:
+  - script:
+      simple: "${a2a:emit('progress...')}"    # optional status events
+  - setBody:
+      constant: "final response"              # consumer handles delivery
+----
+
+The consumer handles delivery regardless of mechanism:
+
+* *Synchronous*: returned directly in the HTTP response
+* *Streaming*: emitted as an SSE message event
+* *Async + polling*: stored in the task's history and status message, returned via `GetTask`
+* *Push notifications*: included in the `COMPLETED` status webhook payload
+
+== Agent Card Resolution
+
+Card fields are resolved with layered precedence (lowest to highest):
+
+1. *Agent card JSON file* — loaded from the URI source (base)
+2. *Bean reference* — `agentCard=#myBean` fills/overrides fields from a programmatic object
+3. *URI parameters* — `name`, `description`, `version` override everything
+
+Bean reference example — useful when the card needs programmatic construction (e.g., dynamic skills):
+
+[source,yaml]
+----
+- route:
+    from:
+      uri: a2a:classpath:agent-card.json
+      parameters:
+        agentCard: "#myCardBean"
+----
+
+URI parameter overrides — customize base cards per environment via properties:
+
+[source,yaml]
+----
+- route:
+    from:
+      uri: a2a:classpath:agent-card.json
+      parameters:
+        name: "{{agent.name}}"
+        version: "{{agent.version}}"
+----
+
+Security schemes from the card drive auth handler selection. Config parameters (`oauthProfile`, `bearerToken`, `apiKey`) provide the runtime credentials and influence scheme priority.
+
+The resolver currently merges these card fields from file and bean cards: `name`, `description`, `url`, `version`, `provider`, `capabilities`, `skills`, `supportedInterfaces`, `securitySchemes`, `securityRequirements`, `iconUrl`, `documentationUrl`, `defaultInputModes`, `defaultOutputModes`, `supportsAuthenticatedExtendedCard`, and unknown extension properties. Legacy input cards using `security` are converted to `securityRequirements`. URI parameters can override only `name`, `descripti [...]
+
+NOTE: The card is loaded once at endpoint startup and cached. Periodic card refresh is not yet implemented.
+
+== HTTP Server Component Discovery
+
+The consumer needs an HTTP server to register A2A endpoints. The discovery order is:
+
+1. *Explicit `httpServerComponent`* parameter (e.g., `undertow`, `jetty`)
+2. *Global `camel.rest.component`* / REST DSL component configuration
+3. *Already registered `platform-http` component*
+4. Exactly one already registered Camel component implementing `RestConsumerFactory`
+5. Exactly one registry bean implementing `RestConsumerFactory`
+
+The preview component does not auto-create arbitrary HTTP server components and does not choose between multiple discovered server factories. Add and register one of the tested server components, or set `httpServerComponent` explicitly.
+
+Tested behavior in this Preview release:
+
+* `camel-platform-http` / Vert.x - suitable for JSON-RPC agents (including SSE streaming) and serving the public agent card. REST custom-method paths containing colons can collide.
+* `camel-undertow` and `camel-jetty` - suitable for REST custom-method paths and real-time SSE streaming.
+
+== Data Format
+
+The `dataFormat` parameter controls what the exchange body contains, following the same convention as the xref:cxf-component.adoc[CXF component]. It applies to both consumer (inbound request) and producer (response) sides.
+
+[cols="1,1,4"]
+|===
+| Value | Default | Description
+
+| `PAYLOAD`
+| Yes
+| Extracts text content from message parts as a `String`. On the consumer, incoming `Message` parts are flattened via `messageToString()`. On the producer, response `Task` or `Message` objects are converted to text. Backward compatible — simple routes using `$\{body}` get clean text. Streaming: same as POJO (lazy iterator on producer, emitter-based on consumer).
+
+| `POJO`
+| No
+| Full Java model objects. On the consumer, the body is the `Message` record with all parts, metadata, and files intact — access individual parts via `$\{body.parts()[0]}`. On the producer, the body is the `Task` or `Message` response object. Streaming: body is a lazy `Iterator<StreamResponse>` parsed on demand (use with Split EIP).
+
+| `RAW`
+| No
+| Raw JSON string with no deserialization. On the consumer, the body is the JSON representation of the incoming `Message`. On the producer, the body is the raw JSON response string. Useful for forwarding, logging, or compliance where byte-exact fidelity matters. Streaming: body is the raw `InputStream` — true SSE passthrough with no buffering.
+|===
+
+Example — consumer in POJO mode for multimodal processing:
+
+[source,yaml]
+----
+- route:
+    from:
+      uri: a2a:classpath:agent-card.json?dataFormat=POJO
+      steps:
+        - log:
+            message: "Received ${body.parts().size()} parts"
+        - setBody:
+            simple: "Processed ${body.parts()[0]}"
+----
+
+Example — producer in RAW mode for proxying:
+
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:proxy
+      steps:
+        - to: a2a:http://remote-agent:8080?dataFormat=RAW
+        - log:
+            message: "Raw JSON: ${body}"
+----
+
+== Task Store
+
+The default `InMemoryTaskStore` manages task state with lazy cleanup. It is thread-safe, using concurrent maps for storage and lock-protected eviction for task-associated data such as message-id mappings, subscribers, and push configs.
+
+The `completedTaskTtl` URI parameter (default 3,600,000 ms / 1 hour) controls the TTL for terminal tasks. Expired tasks are evicted on read or during periodic cleanup.
+
+The following settings are configurable programmatically on the `InMemoryTaskStore` bean, not via URI parameters:
+
+[cols="1,1,3"]
+|===
+| Property | Default | Description
+
+| `maxStoredTasks`
+| `10000`
+| Maximum tasks in the store. When exceeded, the oldest terminal task is evicted; if no terminal task exists, no task is evicted. Set to 0 for unlimited.
+
+| `cleanupInterval`
+| `100`
+| Number of `put()` calls between periodic bulk cleanup runs.
+
+| `stuckTaskTtlMs`
+| `0` (disabled)
+| TTL for non-terminal stuck tasks (`SUBMITTED`, `WORKING`). When set to a positive value, tasks older than this duration are marked `FAILED` on read or periodic cleanup, and subscribers are notified. This preview safety net is disabled by default; prefer `asyncTimeout` on the endpoint for normal timeout handling.
+|===
+
+To customize, register a bean implementing `A2ATaskStore` in the Camel registry. The preview SPI is also split into narrower parent contracts (`A2ATaskRepository`, `A2ATaskSubscriptions`, `A2APushConfigStore`, and `A2ATaskCleanup`) so custom stores can keep storage, subscription, push-config, and cleanup responsibilities separate. Registry-provided stores are wrapped by a guard that enforces terminal-state protection, delegates subscriber registration and notification to the custom store [...]
+
+Custom subscribers can be registered on a task-store bean for audit logging, metrics, or custom delivery:
+
+._Java-only: registering a custom A2ATaskStore with a global subscriber_
+[source,java]
+----
+@BindToRegistry
+public A2ATaskStore taskStore() {
+    MyAuditingTaskStore store = new MyAuditingTaskStore();
+    store.addGlobalSubscriber((taskId, event) -> auditLog.record(taskId, event));
+    return store;
+}
+----
+
+== Model Classes
+
+The component uses Java model classes aligned with A2A v1.0:
+
+[cols="1,3"]
+|===
+| Class | Description
+
+| `Task`
+| Task with `id`, `contextId`, `status` (`TaskStatus`), `history` (`List<Message>`), `artifacts` (`List<Artifact>`), and `metadata` (`Map<String, Object>`). `contextId` is the key for multi-turn conversations (maps to `CamelA2AContextId` header). `Task.latest()` returns the last message in history.
+
+| `Message`
+| Agent or user message with `role`, `parts`, `messageId`, `contextId`, `taskId`, `referenceTaskIds`, `metadata`, and `extensions`. The `Role` enum uses `ROLE_USER`, `ROLE_AGENT`, and `ROLE_UNSPECIFIED`; `ROLE_UNSPECIFIED` is the fallback for unknown role values during deserialization.
+
+| `SendMessageRequest`
+| Operation request wrapper with `message`, `configuration`, and `metadata`. The consumer requires `message.role` and at least one message part.
+
+| `SendMessageConfiguration`
+| Send-message runtime options with `returnImmediately`, `blocking`, `historyLength`, and retained extension properties. `returnImmediately` wins over `blocking`; `blocking=false` is treated as immediate return.
+
+| `SendMessageResponse`
+| Response wrapper containing exactly one of `task` or `message`.
+
+| `TaskListRequest`
+| List-tasks request with `contextId`, `status`, `statusTimestampAfter`, `includeArtifacts`, `historyLength`, `pageSize`, and `pageToken`.
+
+| `ListTasksResponse`
+| List-tasks response with `tasks`, `nextPageToken`, `pageSize`, and `totalSize`.
+
+| `StreamResponse`
+| SSE event wrapper containing exactly one of `task`, `message`, `statusUpdate`, or `artifactUpdate`.
+
+| `TextPart`
+| Text content part implementing `Part<String>`.
+
+| `DataPart`
+| Structured data part implementing `Part<Object>`.
+
+| `FilePart`
+| File content with `raw` for inline base64 data, `url` for referenced content, plus optional `mediaType`, `filename`, and `metadata`.
+
+| `TaskStatus`
+| Status snapshot with `state` (`TaskState`), optional `message` (`Message`), and `timestamp` (`OffsetDateTime`).
+
+| `Artifact`
+| Named output with `artifactId`, `name`, `description`, `parts` (`List<Part<?>>`), `metadata`, and `extensions`.
+
+| `TaskPushNotificationConfig`
+| Push notification webhook config with `id`, `taskId`, `url`, `token` (simple bearer token), and `authentication` (`AuthenticationInfo` with `scheme` + `credentials`). The `token` field provides a simpler alternative to full `authentication` for webhook auth.
+
+| `ListPushNotificationConfigsResponse`
+| Push notification config list response with `configs`.
+|===
+
+Core immutable model types such as `Task`, `Message`, `Artifact`, and `AgentCard` provide builders, for example: `Task.builder().id("t1").contextId("ctx-1").status(new TaskStatus(TaskState.WORKING)).build()`. Mutable request/configuration classes use standard getters and setters.
+
+== Preview API and SPI Boundaries
+
+The stable user-facing surface for this Preview release is the endpoint URI/options, exchange headers, documented model classes, type converters, and these registry SPIs: `A2ATaskStore`, `A2AExtensionHandler`, and `A2ASecuritySchemeHandler`.
+
+The protocol and operation implementation classes under `org.apache.camel.component.a2a.protocol` and `org.apache.camel.component.a2a.operation` are public so the component can share implementation code across packages and tests, but they are not extension SPIs. `A2AProtocol` is sealed deliberately to the built-in REST and JSON-RPC bindings; select a binding with `protocolBinding` rather than implementing a custom protocol class.
+
+The JSON mapper helper returns configured mapper copies. Customizing the returned `ObjectMapper` does not change component-wide serialization behavior.
+
+== Dependencies
+
+The component has zero compile-time coupling to any HTTP library. Transport is discovered at runtime:
+
+[cols="1,2,2"]
+|===
+| Role | SPI | Examples
+
+| Consumer HTTP server
+| `RestConsumerFactory`
+| `camel-platform-http`, `camel-undertow`, `camel-jetty`
+
+| Producer HTTP client
+| Built-in `java.net.http.HttpClient`
+| No additional dependency
+
+| OAuth tokens
+| `OAuthClientAuthenticationFactory`
+| `camel-oauth` (optional, discovered via FactoryFinder)
+
+| Task state
+| `A2ATaskStore`
+| Built-in `InMemoryTaskStore` (default), custom implementations via registry
+|===
+
+Add the HTTP server component you want as a runtime dependency. Consumer routes require one of these dependencies; producer-only routes do not.
+
+[source,xml]
+----
+<!-- Consumer: JSON-RPC or non-streaming HTTP endpoint serving -->
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-platform-http-vertx</artifactId>
+    <version>x.x.x</version>
+    <!-- use the same version as your Camel core version -->
+</dependency>
+
+<!-- Consumer: REST custom-method routes and real-time SSE streaming -->
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-undertow</artifactId>
+    <version>x.x.x</version>
+    <!-- use the same version as your Camel core version -->
+</dependency>
+
+<!-- Alternative consumer transport for REST custom-method routes and real-time SSE streaming -->
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-jetty</artifactId>
+    <version>x.x.x</version>
+    <!-- use the same version as your Camel core version -->
+</dependency>
+
+<!-- Optional: OAuth authentication -->
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-oauth</artifactId>
+    <version>x.x.x</version>
+    <!-- use the same version as your Camel core version -->
+</dependency>
+----
+
+== See Also
+
+* xref:manual::camel-4x-upgrade-guide-4_21.adoc[Camel 4.21 upgrade notes for A2A]
+* https://a2a-protocol.org/latest/specification/[A2A v1.0 Protocol Specification]
+* https://a2a-protocol.org/latest/definitions/[A2A Protocol Definitions]
+* https://github.com/a2aproject/A2A[A2A Protocol GitHub]
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/a2a-consumer.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/a2a-consumer.adoc
new file mode 100644
index 000000000000..50330c6fd2ea
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/a2a-consumer.adoc
@@ -0,0 +1,743 @@
+= A2A - Consumer Guide
+:tabs-sync-option:
+
+xref:ROOT:a2a-component.adoc[Back to A2A Component]
+
+== Consumer — Exposing an A2A Agent
+
+The consumer turns a Camel route into an A2A agent. It automatically:
+
+- Serves the agent card at `GET /.well-known/agent-card.json`
+- Registers HTTP endpoints for A2A operations (REST routes, or a JSON-RPC dispatcher for supported methods)
+- Validates authentication on incoming requests (when configured)
+- Manages task state via an internal `A2ATaskStore`
+- Dispatches push notification webhooks when task state changes
+- Filters inbound `Camel*` and `org.apache.camel.*` headers (case-insensitive) from untrusted requests
+- Enforces `maxPayloadSize` on incoming request bodies (returns 413 when exceeded)
+
+The route's `setBody` output becomes the agent's response — the consumer handles all A2A protocol wrapping. The `dataFormat` parameter controls what the route receives as body: extracted text (`PAYLOAD`, default), the full `Message` object (`POJO`), or raw JSON (`RAW`).
+
+=== Basic Agent (Local Only)
+
+The simplest possible local A2A agent. Define your agent's capabilities in `agent-card.json`, disable operation auth for local-only use, and let the route handle business logic:
+
+[tabs]
+====
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: a2a:classpath:agent-card.json
+      parameters:
+        validateAuth: false
+      steps:
+        - log:
+            message: "Received: ${body}"
+        - setBody:
+            constant: "Hello from my agent!"
+----
+
+Java::
++
+[source,java]
+----
+from("a2a:classpath:agent-card.json?validateAuth=false")
+    .log("Received: ${body}")
+    .setBody(constant("Hello from my agent!"));
+----
+====
+
+Do not use `validateAuth=false` for agents exposed to an untrusted network. See <<Authentication>> for authenticated operation serving.
+
+The agent card (`agent-card.json`) declares your agent's identity and capabilities:
+
+[source,json]
+----
+{
+  "protocolVersion": "1.0",
+  "name": "my-agent",
+  "description": "A simple Camel A2A agent",
+  "url": "http://localhost:8080",
+  "version": "1.0.0",
+  "provider": {
+    "name": "Example",
+    "url": "https://example.com"
+  },
+  "capabilities": {
+    "streaming": false,
+    "pushNotifications": false,
+    "extendedAgentCard": false
+  },
+  "supportedInterfaces": [
+    {
+      "url": "http://localhost:8080",
+      "protocolBinding": "HTTP+JSON",
+      "protocolVersion": "1.0"
+    }
+  ],
+  "defaultInputModes": ["text/plain"],
+  "defaultOutputModes": ["text/plain"],
+  "skills": [
+    {
+      "id": "greet",
+      "name": "Greeting",
+      "description": "Returns a greeting message",
+      "tags": ["greeting"],
+      "examples": ["Say hello to Ada"],
+      "inputModes": ["text/plain"],
+      "outputModes": ["text/plain"]
+    }
+  ]
+}
+----
+
+The component supports the `HTTP+JSON` and `JSONRPC` protocol bindings. The legacy aliases `rest` and `jsonrpc` are also accepted and normalized to the v1.0 binding names. The `protocolVersion`, `defaultInputModes`, and `defaultOutputModes` fields are part of the A2A v1.0 card shape.
+
+NOTE: The `AgentCard` Java model can deserialize A2A v1.0 fields such as `defaultInputModes` and `defaultOutputModes`, and it also stores unknown JSON properties. URI parameter overrides are limited to `name`, `description`, and `version`; the endpoint resolver preserves card metadata and unknown extension properties from file and bean cards, supplies preview defaults for plain-name routes, and rejects unsupported protocol bindings.
+
+=== Card from Parameters (Local Only)
+
+For simple or test agents, the card identity fields can be built from URI parameters - no JSON file needed. Because parameter-built cards do not include security schemes, these local-only examples set `validateAuth=false`:
+
+[tabs]
+====
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: >-
+        a2a:weather-agent
+        ?name=Weather Agent
+        &description=Provides weather forecasts
+        &version=1.0.0
+        &validateAuth=false
+      steps:
+        - bean:
+            ref: weatherService
+----
+
+Java::
++
+[source,java]
+----
+from("a2a:my-agent?name=My Agent&description=A simple agent&version=1.0.0&validateAuth=false")
+    .setBody(constant("Response from parameter-configured agent"));
+----
+====
+
+The component generates the `/.well-known/agent-card.json` response dynamically from the parameters. URI parameters only cover the agent identity fields above; use an agent card file or an `agentCard` bean for capabilities, skills, security schemes, supported interfaces, and other card metadata.
+
+=== JSON-RPC Protocol Binding
+
+By default, the consumer uses the REST binding (HTTP+JSON with colon-notation paths like `/message:send`). To use JSON-RPC 2.0 (single `POST /` endpoint), set `protocolBinding` to `JSONRPC`. The legacy aliases `rest` and `jsonrpc` are also accepted.
+
+[source,yaml]
+----
+- route:
+    from:
+      uri: a2a:classpath:agent-card.json
+      parameters:
+        protocolBinding: JSONRPC
+        validateAuth: false
+      steps:
+        - setBody:
+            constant: "JSON-RPC response"
+----
+
+This example is local-only because it disables operation auth. Keep `validateAuth=true` and configure a card security scheme for network-exposed agents.
+
+The REST binding exposes separate HTTP routes for the operation-serving methods listed in <<Consumer REST API Paths>>. The JSON-RPC binding exposes a single dispatcher and handles `SendMessage`, `SendStreamingMessage`, `GetTask`, `ListTasks`, `CancelTask`, `SubscribeToTask`, and the push notification config operations. Extended agent cards are outside the Preview scope for this first release.
+
+REST requests and responses use `application/a2a+json`. JSON-RPC requests and responses use `application/json`. Streaming operations produce `text/event-stream`.
+
+==== Vert.x Colon-in-Path Issue
+
+The A2A REST protocol uses Google's Custom Method convention with colons in paths (e.g., `/message:send`, `/message:stream`, `/tasks/\{id}:cancel`). Vert.x's router interprets the colon (`:`) as a path parameter delimiter, causing route collisions:
+
+* `/message:send` and `/message:stream` both match the pattern `/message\{param}` — whichever is registered first captures ALL requests
+* `/tasks/\{taskId}:cancel` and `/tasks/\{taskId}:subscribe` can collide with `/tasks/\{taskId}`
+
+This means operation serving is not reliable with REST binding on Vert.x/platform-http. For example, `POST /message:stream` can be handled by the `SendMessage` route instead of the streaming route.
+
+*Workaround:* Use `protocolBinding=JSONRPC` for agents running on Vert.x (the default `platform-http`). Alternatively, use `httpServerComponent=jetty` or `httpServerComponent=undertow`; their routers treat colons as literal characters.
+
+=== Authentication
+
+The component supports OAuth 2.0, OpenID Connect, API key, and HTTP bearer security schemes.
+OAuth 2.0 and OpenID Connect use the `oauthProfile` option and the `camel-oauth` SPI; HTTP bearer can use either an OAuth profile or the static `bearerToken` option.
+
+[IMPORTANT]
+====
+When `validateAuth=true`, the resolved agent card must declare at least one security scheme. If the card declares no schemes, the consumer rejects every request with HTTP 401 (fail closed). Cards built purely from URI parameters contain no security schemes, so combine `validateAuth=true` with a card file or `agentCard` bean that declares the scheme, as shown in the examples below.
+====
+
+[WARNING]
+====
+`validateAuth` defaults to `true`. The well-known agent card remains public, but all A2A operation endpoints require authentication by default. Set `validateAuth=false` only for deployments that intentionally expose unauthenticated A2A operation serving; in that mode the in-memory task store is open/single-tenant and does not provide per-user isolation.
+====
+
+NOTE: The component scopes built-in task and push-notification operations to the authenticated user that created the task. Tenant routing and tenant-aware authorization policy are outside the component scope; implement those rules in the Camel route or in deployment-specific infrastructure.
+
+`securityRequirements` follows A2A v1.0 semantics: multiple requirement objects are alternatives (OR), while multiple schemes inside one requirement must all be satisfied together (AND). The `list` array contains required scopes. The legacy A2A draft field `security` is accepted on input and converted to `securityRequirements`; new cards should use `securityRequirements`.
+
+==== OAuth / OIDC Authentication
+
+Validate incoming bearer tokens via the `camel-oauth` SPI. When an `oauthProfile` is configured, the consumer validates JWT signatures (via JWKS), expiry, issuer, and audience — or uses RFC 7662 token introspection for opaque tokens. Requires `camel-oauth` on the classpath.
+
+[source,yaml]
+----
+- route:
+    from:
+      uri: a2a:classpath:agent-card.json
+      parameters:
+        oauthProfile: my-agent
+        validateAuth: true
+      steps:
+        - setBody:
+            constant: "Authenticated response"
+----
+
+Configure the OIDC provider in application properties (these properties are owned by the `camel-oauth` component — see its documentation for the canonical format):
+
+[source,properties]
+----
+camel.oauth.my-agent.client-id=my-agent-client
+camel.oauth.my-agent.client-secret=my-secret
+camel.oauth.my-agent.token-endpoint=http://keycloak:8180/realms/my-realm/protocol/openid-connect/token
+----
+
+The agent card must declare the security scheme:
+
+[source,json]
+----
+{
+  "securitySchemes": {
+    "oidc": {
+      "openIdConnectSecurityScheme": {
+        "openIdConnectUrl": "http://keycloak:8180/realms/my-realm/.well-known/openid-configuration"
+      }
+    }
+  },
+  "securityRequirements": [
+    {
+      "schemes": {
+        "oidc": {
+          "list": []
+        }
+      }
+    }
+  ]
+}
+----
+
+When authentication succeeds, the `CamelA2AUserProfile` exchange property is populated with a `Map<String, Object>` containing the authenticated user's profile (subject, issuer, scopes, claims). When using OAuth/OIDC, the full `OAuthTokenValidationResult` is also available as the `CamelOAuthTokenValidationResult` exchange property.
+
+==== API Key Authentication
+
+The `apiKeyHeader` parameter controls which HTTP header carries the API key. It defaults to `Authorization`. A common override is `X-API-Key`:
+
+[source,yaml]
+----
+- route:
+    from:
+      uri: a2a:classpath:agent-card.json
+      parameters:
+        validateAuth: true
+        apiKey: "{{my.api.key}}"
+        apiKeyHeader: X-API-Key      # default is Authorization
+      steps:
+        - setBody:
+            constant: "API key protected response"
+----
+
+The agent card must declare an `apiKey` security scheme:
+
+[source,json]
+----
+{
+  "securitySchemes": {
+    "apikey": {
+      "apiKeySecurityScheme": {
+        "location": "header",
+        "name": "X-API-Key"
+      }
+    }
+  },
+  "securityRequirements": [
+    {
+      "schemes": {
+        "apikey": {
+          "list": []
+        }
+      }
+    }
+  ]
+}
+----
+
+When the scheme declares `location=header` and `name`, that header name takes precedence over `apiKeyHeader`. The component also supports `location=query` and `location=cookie` for API key schemes.
+
+==== Bearer Token
+
+[source,yaml]
+----
+- route:
+    from:
+      uri: a2a:classpath:agent-card.json
+      parameters:
+        bearerToken: "{{my.token}}"
+        validateAuth: true
+      steps:
+        - setBody:
+            constant: "Bearer token protected response"
+----
+
+The agent card must declare an `http` bearer security scheme:
+
+[source,json]
+----
+{
+  "securitySchemes": {
+    "bearer": {
+      "httpAuthSecurityScheme": {
+        "scheme": "bearer"
+      }
+    }
+  },
+  "securityRequirements": [
+    {
+      "schemes": {
+        "bearer": {
+          "list": []
+        }
+      }
+    }
+  ]
+}
+----
+
+NOTE: The agent card endpoint (`GET /.well-known/agent-card.json`) is always public — clients need it for discovery before they can authenticate.
+
+=== SSE Streaming with `${a2a:emit()}`
+
+Agents can emit progressive status updates during processing using the `${a2a:emit()}` Simple language function. Clients receive these as Server-Sent Events (SSE).
+
+For `SendStreamingMessage` and `SubscribeToTask`, the agent card must explicitly set `capabilities.streaming=true`. If the `capabilities` object is missing, or `streaming` is omitted or `false`, the consumer returns `UnsupportedOperationError` (HTTP 405 for REST, JSON-RPC `-32004` for JSON-RPC).
+
+[tabs]
+====
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: a2a:classpath:agent-card.json
+      parameters:
+        protocolBinding: JSONRPC
+        httpServerComponent: undertow
+      steps:
+        - script:
+            simple: "${a2a:emit('Connecting to database...')}"
+        - delay:
+            constant: 2000
+        - script:
+            simple: "${a2a:emit('Processing 1000 records...')}"
+        - delay:
+            constant: 3000
+        - script:
+            simple: "${a2a:emit('Analysis complete!')}"
+        - setBody:
+            constant: "Final analysis results: ..."
+----
+
+Java::
++
+[source,java]
+----
+import org.apache.camel.component.a2a.A2AProgress;
+
+from("a2a:classpath:agent-card.json?httpServerComponent=undertow")
+    .process(exchange -> {
+        A2AProgress.emit(exchange, "Connecting...");
+        //connect to the external service
+        A2AProgress.emit(exchange, "Processing...");
+        //process data
+        exchange.getMessage().setBody("Here is the final answer.");
+    });
+----
+====
+
+Each `${a2a:emit('message')}` emits an SSE status event with `TASK_STATE_WORKING` state. The final `setBody` is automatically delivered as the completed response.
+
+You can also emit with an explicit state:
+
+[source,yaml]
+----
+- script:
+    simple: "${a2a:emit(INPUT_REQUIRED, 'Please provide your address')}"
+----
+
+NOTE: Use `script` EIP (not `setBody`) for `${a2a:emit()}` calls — `script` evaluates the expression for its side effect without changing the message body. Use `setBody` only for the final response.
+
+=== Scoped progress updates with `a2aSubTask`
+
+Camel routes can group related work with the `a2aSubTask` EIP and emit progress updates before, after, or when the grouped steps fail.
+This is a regular Camel route step, not a YAML-only extension, and it can be used from Camel's model-based DSLs when `camel-a2a` is on the classpath.
+The `emitBefore`, `emitAfter`, and `emitOnError` fields are optional and are evaluated as Simple expressions against the current Exchange.
+The nested `steps` behave like normal Camel route steps: in YAML they are configured under `steps`, and in Java DSL they are added after `.a2aSubTask()` until `.end()`.
+If the nested steps fail, `emitOnError` can access the original exception, for example with `$\{exception.message}`, and the original exception continues to propagate through the route.
+Failures while evaluating the `emitBefore`, `emitAfter`, or `emitOnError` Simple expressions are route failures.
+Failures while storing or notifying the resulting A2A progress event are best-effort: they are logged at debug level and do not stop nested work, fail an otherwise successful exchange, or replace the original nested-step exception.
+By default, emitting progress outside an active A2A task context is a no-op.
+Set `failIfNoTaskContext=true` when a route should fail instead if the current Exchange does not carry an active A2A task.
+An active task context is normally created by an A2A consumer while it is processing a task.
+Use stable `id` values on long-lived sub-tasks so route tracing and route-structure views keep stable node names.
+
+[source,yaml]
+----
+- route:
+    from:
+      uri: a2a:classpath:agent-card.json
+      parameters:
+        protocolBinding: JSONRPC
+        httpServerComponent: undertow
+        validateAuth: false
+      steps:
+        - a2aSubTask:
+            id: search-docs-progress
+            emitBefore: "Searching docs..."
+            emitAfter: "Docs found: ${body.size()}"
+            emitOnError: "Error searching docs: ${exception.message}"
+            failIfNoTaskContext: true
+            steps:
+              - to:
+                  uri: "elasticsearch:docs?operation=Search"
+        - a2aSubTask:
+            id: draft-answer-progress
+            emitBefore: "Drafting answer..."
+            emitAfter: "Answer drafted: ${body}"
+            emitOnError: "Error drafting answer: ${exception.message}"
+            steps:
+              - bean:
+                  ref: answerDraftingService
+                  method: draft
+        - setBody:
+            simple: "Final answer: ${body}"
+----
+
+The route examples in this section are local-only because they disable operation auth. Keep `validateAuth=true` and configure a card security scheme for network-exposed agents.
+
+The same route step is also available from Java DSL:
+
+[source,java]
+----
+from("a2a:classpath:agent-card.json?protocolBinding=JSONRPC&httpServerComponent=undertow&validateAuth=false")
+    .a2aSubTask()
+        .id("search-docs-progress")
+        .emitBefore("Searching docs...")
+        .emitAfter("Docs found: ${body.size()}")
+        .emitOnError("Error searching docs: ${exception.message}")
+        .failIfNoTaskContext(true)
+        .to("elasticsearch:docs?operation=Search")
+    .end();
+----
+
+For advanced use cases, `A2AProgress` also supports emitting structured artifacts and intermediate messages:
+
+._Java-only: emitting structured artifacts and intermediate messages with A2AProgress_
+[source,java]
+----
+// Emit a structured artifact (e.g., a generated file)
+Artifact artifact = Artifact.builder()
+    .artifactId("report-1")
+    .name("Analysis Report")
+    .parts(List.of(new TextPart("Report content...")))
+    .build();
+A2AProgress.emitArtifact(exchange, artifact, false, true);  // append=false, lastChunk=true
+
+// Emit an intermediate agent message (not a status update)
+Message msg = Message.builder()
+    .role(Message.Role.ROLE_AGENT)
+    .parts(List.of(new TextPart("Intermediate finding...")))
+    .build();
+A2AProgress.emitMessage(exchange, msg);
+----
+
+The consumer supports two SSE streaming patterns:
+
+* *`SendStreamingMessage`* — The stream starts with the submitted `Task`, followed by progress events from `A2AProgress` or `${a2a:emit()}`. When the route completes, the body is emitted as the final message.
+* *`SubscribeToTask`* — Clients subscribe via `POST /tasks/\{id}:subscribe` to receive real-time SSE updates for an existing non-terminal task. The component uses an Event-to-Stream Bridge (`QueueStreamEmitter` + `SseQueueInputStream`) with heartbeat comments to keep the connection alive. The stream sends the current `Task` first and ends when the task later reaches a terminal state. Subscribing to an already-terminal task returns `UnsupportedOperationError`.
+
+[NOTE]
+====
+*HTTP Server Component for Streaming*
+
+Real-time SSE streaming works with all tested HTTP server components: Vert.x/platform-http, Undertow, and Jetty.
+====
+
+SSE streaming parameters:
+
+* `sseHeartbeatInterval` (default 15,000 ms / 15 seconds) — interval for SSE keep-alive heartbeat comments (`:` lines) sent to prevent proxies from closing idle connections. Independent from `asyncTimeout`.
+* `sseQueueCapacity` (default 1,000) — maximum SSE events buffered per streaming connection. When the queue is full, new events are dropped with a warning log. Prevents unbounded memory growth from slow clients.
+
+=== Async Tasks with `returnImmediately`
+
+For long-running operations, enable `returnImmediately` to return a `SUBMITTED` task immediately. The route processes in the background, and clients poll with `GetTask`:
+
+[source,yaml]
+----
+- route:
+    from:
+      uri: a2a:classpath:agent-card.json
+      parameters:
+        returnImmediately: true
+        asyncTimeout: 30000          # default is 300000 (5 minutes)
+      steps:
+        - delay:
+            constant: 10000
+        - setBody:
+            constant: "Long computation result"
+----
+
+The `asyncTimeout` parameter (default: 300,000 ms / 5 minutes) controls how long the background processing can run before the task is marked `FAILED`.
+
+The consumer manages the task lifecycle automatically: `SUBMITTED` -> `WORKING` -> `COMPLETED` (or `FAILED` on error / timeout).
+
+`returnImmediately` resolution priority (highest wins):
+
+1. Per-request: `configuration.returnImmediately` in the `SendMessageRequest` body
+2. Per-request: `configuration.blocking=false` in the `SendMessageRequest` body (typed inverse of immediate return)
+3. Per-exchange: `CamelA2AReturnImmediately` header
+4. Endpoint config: `returnImmediately` URI parameter
+
+`SendMessageRequest.configuration` is modeled as `SendMessageConfiguration`. The consumer interprets `returnImmediately`, `blocking`, and `historyLength`; unknown fields are retained for protocol extensions and future A2A options. `configuration.historyLength` limits the task history returned by synchronous `SendMessage` task responses.
+
+NOTE: The REST consumer rejects `returnImmediately` for streaming operations (`SendStreamingMessage`) with 400 Bad Request.
+
+=== Push Notifications
+
+Agents that use `returnImmediately` can deliver updates via webhooks. Clients register a webhook URL via `CreateTaskPushNotificationConfig`, and the component's built-in `PushNotificationDispatcher` sends status updates to registered URLs.
+
+The agent card should declare push notification support so clients can discover the feature:
+
+[source,json]
+----
+{
+  "capabilities": {
+    "pushNotifications": true
+  }
+}
+----
+
+Progress updates emitted via `${a2a:emit()}` or `A2AProgress.emit()` are automatically dispatched to all registered webhooks.
+
+Push notification dispatch features:
+
+* *Parallel dispatch* — multiple webhooks per task are notified concurrently via `CompletableFuture`
+* *Auth headers* — `AuthenticationInfo` from the push config is sent as `Authorization: <scheme> <credentials>`
+* *Retry with exponential backoff* — configurable via `pushRetryAttempts` (default 3) and `pushRetryBackoffMs` (default 1s). Backoff formula: `delay x 2^attempt`. Only retries on 5xx/IOException — client errors (4xx) are not retried
+* *410 Gone auto-cleanup* — webhooks returning HTTP 410 are automatically deregistered
+* *SSRF protection* — webhook URLs are validated at registration time (blocks private IPs, loopback, link-local, wildcard, and cloud metadata addresses). Non-loopback webhook URLs must use HTTPS. Set `allowLocalWebhookUrls=true` to permit loopback URLs (plain HTTP allowed) for local development only
+
+=== Capacity Limiting
+
+Control concurrent task processing and queue overflow:
+
+[source,yaml]
+----
+- route:
+    from:
+      uri: a2a:classpath:agent-card.json
+      parameters:
+        maxConcurrentTasks: 10
+        taskQueueSize: 50
+      steps:
+        - setBody:
+            constant: "Processing..."
+----
+
+[cols="1,1,3"]
+|===
+| Parameter | Default | Description
+
+| `maxConcurrentTasks`
+| `0` (unlimited)
+| Maximum concurrent tasks. A shared semaphore governs all processing paths (sync, async, streaming).
+
+| `taskQueueSize`
+| `0` (no queue)
+| Pending queue capacity for async requests when all slots are occupied. Synchronous and streaming requests cannot be queued — they are rejected immediately.
+|===
+
+Behavior by processing path:
+
+* *Synchronous* (`returnImmediately=false`): if no permit, returns `ServerBusyError` (HTTP 429)
+* *Asynchronous* (`returnImmediately=true`): if no permit and queue has space, task queues as `SUBMITTED`; otherwise HTTP 429
+* *Streaming* (`SendStreamingMessage`): same as synchronous — rejects immediately
+
+The error response follows the A2A error model: REST returns HTTP 429 with `ServerBusyError`; JSON-RPC returns code `-32000` in the JSON-RPC error envelope.
+
+On shutdown, queued tasks are marked `FAILED` and subscribers are notified.
+
+=== Payload Size Limits
+
+The consumer enforces `maxPayloadSize` (default 6,291,456 bytes / 6 MiB) on incoming request bodies. Requests exceeding this limit receive HTTP 413 (REST) or a JSON-RPC error.
+
+[source,yaml]
+----
+- route:
+    from:
+      uri: a2a:classpath:agent-card.json
+      parameters:
+        maxPayloadSize: 10485760
+----
+
+=== CORS Support
+
+To enable CORS (required when browsers call your agent directly), set the REST configuration:
+
+[source,properties]
+----
+camel.rest.enableCors=true
+----
+
+The consumer automatically adds `Access-Control-*` headers (including A2A-specific headers like `A2A-Version` and `A2A-Extensions`) and registers OPTIONS preflight handlers for all A2A paths.
+
+=== A2A Extensions
+
+The agent card can advertise protocol extensions in `capabilities.extensions`. For protected operation routes, clients can request extensions with the `A2A-Extensions` HTTP header as a comma-separated list of extension URIs.
+
+The consumer validates requested extensions against the resolved agent card. If any requested URI is not advertised, or if a card extension marked `required=true` is not requested, the request fails before route processing with `UnsupportedExtensionError`. Accepted extension URIs are exposed to the route as the `CamelA2AExtensions` header and exchange property, and are echoed in the `A2A-Extensions` response header.
+
+Routes can branch directly on `CamelA2AExtensions`. For reusable behavior, register one or more `org.apache.camel.component.a2a.extension.A2AExtensionHandler` beans in the Camel registry. A handler is matched by extension URI and is invoked before and after route processing when that extension is negotiated. The handler receives the full `AgentExtension` declaration from the agent card, including `params`.
+
+=== Consumer REST API Paths
+
+When using the default REST protocol binding, the consumer registers these HTTP endpoints:
+
+[cols="1,2,2"]
+|===
+| Method | Path | Operation
+
+| `GET`
+| `/.well-known/agent-card.json`
+| Agent card discovery (always public)
+
+| `POST`
+| `/message:send`
+| SendMessage
+
+| `POST`
+| `/message:stream`
+| SendStreamingMessage (SSE response)
+
+| `GET`
+| `/tasks`
+| ListTasks
+
+| `GET`
+| `/tasks/\{taskId}`
+| GetTask
+
+| `POST`
+| `/tasks/\{taskId}:cancel`
+| CancelTask
+
+| `POST`
+| `/tasks/\{taskId}:subscribe`
+| SubscribeToTask (SSE response)
+
+| `POST`
+| `/tasks/\{taskId}/pushNotificationConfigs`
+| CreateTaskPushNotificationConfig
+
+| `GET`
+| `/tasks/\{taskId}/pushNotificationConfigs`
+| ListTaskPushNotificationConfigs
+
+| `GET`
+| `/tasks/\{taskId}/pushNotificationConfigs/\{configId}`
+| GetTaskPushNotificationConfig
+
+| `DELETE`
+| `/tasks/\{taskId}/pushNotificationConfigs/\{configId}`
+| DeleteTaskPushNotificationConfig
+|===
+
+All paths are prefixed with `basePath` if configured. When using JSON-RPC binding, a single `POST /` endpoint dispatches based on the JSON-RPC `method` field.
+
+The built-in `ListTasks` consumer applies `contextId`, `status`, `statusTimestampAfter`, `pageSize`, `pageToken`, `includeArtifacts`, and `historyLength`. `pageSize` defaults to `50` and is capped at `100`. `pageToken` values returned by the consumer are opaque cursor tokens containing a snapshot of the filtered task IDs for that listing. Clients must send the token back unchanged with the same filters; numeric offsets are rejected.
+
+=== Consumer Error Responses
+
+REST binding responses use the A2A v1.0 error wrapper with an `error` object. The `ErrorInfo.reason` detail maps back to these component error names:
+
+[cols="2,1,2"]
+|===
+| Condition | HTTP status | Error code
+
+| Unsupported `A2A-Version` request header
+| `400`
+| `VersionNotSupportedError`
+
+| Authentication validation failure
+| `401`
+| `AuthenticationError`
+
+| Authenticated caller is not authorized for the task
+| `403`
+| `AuthorizationError`
+
+| Unsupported requested extension, or required extension not requested
+| `400`
+| `ExtensionSupportRequiredError`
+
+| Empty `SendMessage` or `SendStreamingMessage` body
+| `400`
+| `ContentTypeNotSupportedError`
+
+| Request body larger than `maxPayloadSize`
+| `413`
+| `ContentTypeNotSupportedError`
+
+| Streaming or task subscription requested but `capabilities.streaming` is omitted or `false`
+| `405`
+| `UnsupportedOperationError`
+
+| Push notification config requested but `capabilities.pushNotifications` is omitted or `false`
+| `405`
+| `UnsupportedOperationError`
+
+| `returnImmediately=true` on REST `SendStreamingMessage`
+| `400`
+| `UnsupportedOperationError`
+
+| Invalid parameters (for example negative `historyLength`, invalid `pageSize`, invalid `pageToken`, or rejected webhook URL)
+| `400`
+| `InvalidParamsError`
+
+| Agent capacity reached
+| `429`
+| `ServerBusyError`
+
+| Task or push notification config not found
+| `404`
+| `TaskNotFoundError`
+
+| Cancel requested for a terminal task
+| `409`
+| `TaskNotCancelableError`
+
+| Unhandled consumer exception
+| `500`
+| `InternalError`
+|===
+
+REST binding returns these error responses as `application/a2a+json` with an `error` object containing the HTTP status, status name, message, and a `google.rpc.ErrorInfo` detail reason such as `TASK_NOT_FOUND` or `VERSION_NOT_SUPPORTED`.
+
+JSON-RPC binding returns JSON-RPC error envelopes as `application/json`. Parse errors use `-32700`, invalid requests use `-32600`, unknown methods use `-32601`, invalid parameters use `-32602`, internal errors use `-32603`, capacity and authorization errors use `-32000`, missing tasks use `-32001`, non-cancelable terminal tasks use `-32002`, push notification support errors use `-32003`, unsupported operations use `-32004`, unsupported content types use `-32005`, invalid agent responses  [...]
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/a2a-producer.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/a2a-producer.adoc
new file mode 100644
index 000000000000..a624caf5c7ed
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/a2a-producer.adoc
@@ -0,0 +1,377 @@
+= A2A - Producer Guide
+:tabs-sync-option:
+
+xref:ROOT:a2a-component.adoc[Back to A2A Component]
+
+== Producer — Calling a Remote Agent
+
+The producer calls a remote A2A agent. It automatically discovers the agent card, selects the protocol binding, acquires credentials, and wraps/unwraps messages.
+
+=== Basic Call
+
+[tabs]
+====
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:call-agent
+      steps:
+        - setBody:
+            constant: "What is the weather?"
+        - to:
+            uri: a2a:http://remote-agent:8080
+        - log:
+            message: "Agent replied: ${a2a:text}"
+----
+
+Java::
++
+[source,java]
+----
+from("direct:call-agent")
+    .setBody(constant("What is the weather?"))
+    .to("a2a:http://remote-agent:8080")
+    .log("Agent replied: ${a2a:text}");
+----
+====
+
+The producer:
+
+1. Fetches the agent card from `\http://remote-agent:8080/.well-known/agent-card.json`
+2. Wraps the body as an A2A `SendMessage` request
+3. Sends the request using the card's declared protocol binding
+4. Returns the response as the exchange body — by default (`dataFormat=PAYLOAD`) as extracted text; with `dataFormat=POJO` as the full `Task` or `Message` Java object
+
+=== Authenticated Calls
+
+==== OIDC (Client Credentials)
+
+[source,yaml]
+----
+- to:
+    uri: a2a:http://remote-agent:8080
+    parameters:
+      oauthProfile: my-profile
+----
+
+Acquires a token via client-credentials grant, caches it, and refreshes on expiry.
+
+==== API Key
+
+[source,yaml]
+----
+- to:
+    uri: a2a:http://remote-agent:8082
+    parameters:
+      apiKey: "{{my.api.key}}"
+      apiKeyHeader: X-API-Key
+----
+
+==== Bearer Token
+
+[source,yaml]
+----
+- to:
+    uri: a2a:http://remote-agent:8080
+    parameters:
+      bearerToken: "{{my.token}}"
+----
+
+=== JSON-RPC Producer
+
+[source,yaml]
+----
+- to:
+    uri: a2a:http://remote-agent:8081
+    parameters:
+      protocolBinding: JSONRPC
+----
+
+=== Producer Streaming
+
+The producer supports two streaming modes, controlled by the `dataFormat` parameter.
+
+==== Default (PAYLOAD/POJO): Lazy Iterator
+
+The exchange body is a `SseEventIterator` (implements `Iterator<StreamResponse>` + `Closeable`) that parses SSE events lazily from the remote agent's response stream. Each call to `next()` blocks until the next event arrives. Use with the Split EIP for event-by-event processing:
+
+[tabs]
+====
+YAML::
++
+[source,yaml]
+----
+- setHeader:
+    name: CamelA2AOperation
+    constant: MESSAGE_STREAM
+- to: a2a:https://agent.example.com
+- split:
+    simple: "${body}"
+    streaming: true
+    steps:
+      - choice:
+          when:
+            - simple: "${body.statusUpdate} != null"
+              steps:
+                - log:
+                    message: "Progress: ${body.statusUpdate.status.state}"
+            - simple: "${body.message} != null"
+              steps:
+                - log:
+                    message: "Final message received"
+----
+
+Java::
++
+[source,java]
+----
+from("direct:stream")
+    .setHeader("CamelA2AOperation", constant("MESSAGE_STREAM"))
+    .to("a2a:https://agent.example.com")
+    .split(body()).streaming()
+        .log("Event: ${body}")
+    .end();
+----
+====
+
+The iterator implements `Closeable`, so Camel's Split EIP automatically releases the underlying HTTP connection after iteration.
+
+To buffer all events into a `List<StreamResponse>`:
+
+[source,yaml]
+----
+- to: a2a:https://agent.example.com
+- convertBodyTo:
+    type: java.util.List
+----
+
+==== Raw Passthrough (RAW mode)
+
+With `dataFormat=RAW`, the exchange body is the raw `InputStream` from the remote agent's SSE response. No parsing or buffering — bytes flow through untouched. Ideal for proxying SSE streams to a browser:
+
+[tabs]
+====
+YAML::
++
+[source,yaml]
+----
+- to:
+    uri: a2a:https://agent.example.com?dataFormat=RAW
+    parameters:
+      operation: MESSAGE_STREAM
+- setHeader:
+    name: Content-Type
+    constant: text/event-stream
+----
+
+Java::
++
+[source,java]
+----
+from("platform-http:/stream")
+    .to("a2a:https://agent.example.com?dataFormat=RAW&operation=MESSAGE_STREAM")
+    .setHeader("Content-Type", constant("text/event-stream"));
+----
+====
+
+==== Subscribe to Task Updates
+
+Subscribe to ongoing task updates from a remote agent:
+
+[source,yaml]
+----
+- setHeader:
+    name: CamelA2AOperation
+    constant: TASK_SUBSCRIBE
+- setHeader:
+    name: CamelA2ATaskId
+    simple: "${exchangeProperty.taskId}"
+- to: a2a:https://agent.example.com
+- split:
+    simple: "${body}"
+    streaming: true
+    steps:
+      - log:
+          message: "Task update: ${body.statusUpdate.status.state}"
+----
+
+Streaming requests use `asyncTimeout` (default 5 minutes) instead of the standard 60-second request timeout. SSE heartbeat comments from the remote agent are automatically filtered during parsing.
+
+=== Async Task Lifecycle (returnImmediately + GetTask Polling)
+
+[source,yaml]
+----
+# Step 1: Submit the task
+- setBody:
+    constant: "Start long operation"
+- to:
+    uri: a2a:http://remote-agent:8083
+    parameters:
+      oauthProfile: assistant
+- setVariable:
+    name: taskId
+    simple: "${header.CamelA2ATaskId}"
+
+# Step 2: Poll for completion
+- removeHeaders:
+    pattern: "*"
+- setHeader:
+    name: CamelA2AOperation
+    constant: TASK_GET
+- setHeader:
+    name: CamelA2ATaskId
+    simple: "${variable.taskId}"
+- to:
+    uri: a2a:http://remote-agent:8083
+    parameters:
+      oauthProfile: assistant
+----
+
+=== Push Notification Registration
+
+[source,yaml]
+----
+# Step 1: Submit task
+- setBody:
+    constant: "Track my package"
+- to: a2a:http://remote-agent:8085
+- setVariable:
+    name: taskId
+    simple: "${header.CamelA2ATaskId}"
+
+# Step 2: Register push notification webhook
+- removeHeaders:
+    pattern: "*"
+- setHeader:
+    name: CamelA2AOperation
+    constant: PUSH_CONFIG_CREATE
+- setHeader:
+    name: CamelA2ATaskId
+    simple: "${variable.taskId}"
+- setBody:
+    simple: "${ref:pushConfig}"
+- to: a2a:http://remote-agent:8085
+----
+
+Configure the webhook URL as a bean:
+
+[source,properties]
+----
+camel.beans.pushConfig = #class:org.apache.camel.component.a2a.model.TaskPushNotificationConfig
+camel.beans.pushConfig.url = https://my-server:8090/webhook
+----
+
+The full push notification config CRUD is also available. `PUSH_CONFIG_GET` and `PUSH_CONFIG_DELETE` require both `CamelA2ATaskId` and `CamelA2APushConfigId`. Use JSON-RPC binding for these two producer operations when addressing another `camel-a2a` agent with separate task and config IDs.
+
+[source,yaml]
+----
+# List push configs for a task
+- setHeader:
+    name: CamelA2AOperation
+    constant: PUSH_CONFIG_LIST
+- setHeader:
+    name: CamelA2ATaskId
+    simple: "${variable.taskId}"
+- to: a2a:https://agent.example.com
+
+# Get a specific push config
+- setHeader:
+    name: CamelA2AOperation
+    constant: PUSH_CONFIG_GET
+- setHeader:
+    name: CamelA2ATaskId
+    simple: "${variable.taskId}"
+- setHeader:
+    name: CamelA2APushConfigId
+    simple: "${variable.configId}"
+- to: "a2a:https://agent.example.com?protocolBinding=JSONRPC"
+
+# Delete a push config
+- setHeader:
+    name: CamelA2AOperation
+    constant: PUSH_CONFIG_DELETE
+- setHeader:
+    name: CamelA2ATaskId
+    simple: "${variable.taskId}"
+- setHeader:
+    name: CamelA2APushConfigId
+    simple: "${variable.configId}"
+- to: "a2a:https://agent.example.com?protocolBinding=JSONRPC"
+----
+
+=== Parallel Multicast
+
+Call multiple agents concurrently using Camel's `multicast` EIP:
+
+[source,yaml]
+----
+- multicast:
+    parallelProcessing: true
+    aggregationStrategy: "#class:MyAggregator"
+    steps:
+      - to: direct:call-weather
+      - to: direct:call-news
+      - to: direct:call-fortune
+
+- route:
+    id: call-weather
+    from:
+      uri: direct:call-weather
+      steps:
+        - removeHeaders:
+            pattern: "*"
+        - setBody:
+            constant: "What is the weather?"
+        - to:
+            uri: a2a:http://weather-agent:8080
+            parameters:
+              oauthProfile: my-profile
+----
+
+[TIP]
+====
+Use `removeHeaders: "*"` before each producer call in a multicast branch to prevent leaking headers (like `CamelA2ATaskId`) from one branch to another.
+====
+
+=== Address Override
+
+Override the remote agent's URL from the card using `host`/`port`/`basePath` config:
+
+[source,yaml]
+----
+- to: a2a:https://agent.example.com?host=http://localhost&port=8080
+----
+
+Priority without producer credentials: `host` config > card's `supportedInterfaces` URL > `agentCardSource` URL. When producer credentials are configured (`apiKey`, `bearerToken`, or `oauthProfile`) and `host` is not set, the producer sends credentialed requests only to the HTTP(S) `agentCardSource` origin. This avoids sending credentials to a URL supplied by the remote card's `supportedInterfaces` field. The `port` and `basePath` producer overrides are applied when `host` is configured. [...]
+
+NOTE: The producer does not forward arbitrary inbound `Authorization` or `Cookie` headers. Only credentials resolved from the A2A endpoint configuration are applied to outgoing requests.
+
+=== Redirect Handling
+
+By default, the producer does not follow HTTP redirects to prevent credential leakage on cross-origin redirects. Enable only when the remote agent is known to issue redirects:
+
+[source,yaml]
+----
+- to: a2a:https://agent.example.com?followRedirects=true
+----
+
+NOTE: `followRedirects` applies to operation requests only. Agent card discovery never follows redirects — a card URL that returns a redirect fails with an error.
+
+Producer operation responses must be 2xx. Redirect and other non-2xx responses fail before response deserialization, so a 3xx response cannot be accidentally parsed as an A2A payload.
+
+=== Request Timeouts
+
+The producer uses different timeouts depending on the operation:
+
+* *Non-streaming requests*: hard-coded at 60 seconds. There is currently no configuration parameter to override this.
+* *Streaming requests* (`SendStreamingMessage`, `SubscribeToTask`): uses `asyncTimeout` (default 300,000 ms / 5 minutes).
+* *Streaming read timeout*: `streamingReadTimeout` (default 300,000 ms / 5 minutes) — if no SSE event arrives from the remote agent within this period, the stream is closed with an error. Prevents indefinite blocking when a remote agent stops sending events.
+* *Streaming event size*: each decoded SSE event is limited by `maxPayloadSize` (default 6 MiB). Oversized events fail the producer stream instead of accumulating unbounded memory.
+* *TCP connection*: `connectTimeout` (default 30,000 ms / 30 seconds).
+
+=== A2A-Version Header
+
+The producer sends an `A2A-Version: 1.0` header on every outgoing operation request, per the A2A v1.0 specification. This is automatic and not configurable.
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/activemq-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/activemq-component.adoc
new file mode 100644
index 000000000000..c1adbaaebe5e
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/activemq-component.adoc
@@ -0,0 +1,144 @@
+= ActiveMQ 5.x Component
+:doctitle: ActiveMQ 5.x
+:shortname: activemq
+:artifactid: camel-activemq
+:description: Send messages to (or consume from) Apache ActiveMQ 5.x. This component extends the Camel JMS component.
+:since: 1.0
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Both producer and consumer are supported
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The ActiveMQ component is an extension to the JMS component and has been pre-configured for using Apache ActiveMQ 5.x (not Artemis).
+Users of Apache ActiveMQ Artemis should use the JMS component.
+
+[IMPORTANT]
+====
+The camel-activemq component is best intended for ActiveMQ 5.x classic brokers. If you use ActiveMQ 6.x brokers,
+then use the camel-activemq6 component instead.
+====
+
+[TIP]
+====
+*More documentation*
+
+See the JMS component for more documentation and examples
+====
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+[source,xml]
+------------------------------------------------------------
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-activemq</artifactId>
+    <version>x.x.x</version>
+    <!-- use the same version as your Camel core version -->
+</dependency>
+------------------------------------------------------------
+
+== URI format
+
+--------------------------------------------
+activemq:[queue:|topic:]destinationName[?options]
+--------------------------------------------
+
+Where `destinationName` is a JMS queue or topic name. By default, the
+`destinationName` is interpreted as a queue name. For example, to
+connect to the queue, `foo` use:
+
+-----------
+activemq:foo
+-----------
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+== Examples
+
+You'll need to provide a connectionFactory to the ActiveMQ Component, to have the following examples working.
+
+=== Producer Example
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("timer:mytimer?period=5000")
+    .setBody(constant("HELLO from Camel!"))
+    .to("activemq:queue:HELLO.WORLD");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="timer:mytimer?period=5000"/>
+  <setBody>
+    <constant>HELLO from Camel!</constant>
+  </setBody>
+  <to uri="activemq:queue:HELLO.WORLD"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: timer:mytimer
+      parameters:
+        period: 5000
+      steps:
+        - setBody:
+            constant: "HELLO from Camel!"
+        - to:
+            uri: activemq:queue:HELLO.WORLD
+----
+====
+
+=== Consumer Example
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("activemq:queue:HELLO.WORLD")
+    .log("Received a message - ${body}");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="activemq:queue:HELLO.WORLD"/>
+  <log message="Received a message - ${body}"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: activemq:queue:HELLO.WORLD
+      steps:
+        - log:
+            message: "Received a message - ${body}"
+----
+====
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/activemq6-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/activemq6-component.adoc
new file mode 100644
index 000000000000..d05cbdce1a20
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/activemq6-component.adoc
@@ -0,0 +1,144 @@
+= ActiveMQ 6.x Component
+:doctitle: ActiveMQ 6.x
+:shortname: activemq6
+:artifactid: camel-activemq6
+:description: Send messages to (or consume from) Apache ActiveMQ 6.x. This component extends the Camel JMS component.
+:since: 4.7
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Both producer and consumer are supported
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The ActiveMQ component is an extension to the JMS component and has been pre-configured for using Apache ActiveMQ 6.x (not Artemis).
+Users of Apache ActiveMQ Artemis should use the JMS component.
+
+[IMPORTANT]
+====
+The camel-activemq6 component is best intended for ActiveMQ 6.x brokers. If you use ActiveMQ 5.x brokers,
+then use the camel-activemq 5.x component instead.
+====
+
+[TIP]
+====
+*More documentation*
+
+See the JMS component for more documentation and examples
+====
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+[source,xml]
+------------------------------------------------------------
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-activemq6</artifactId>
+    <version>x.x.x</version>
+    <!-- use the same version as your Camel core version -->
+</dependency>
+------------------------------------------------------------
+
+== URI format
+
+--------------------------------------------
+activemq:[queue:|topic:]destinationName[?options]
+--------------------------------------------
+
+Where `destinationName` is a JMS queue or topic name. By default, the
+`destinationName` is interpreted as a queue name. For example, to
+connect to the queue, `foo` use:
+
+-----------
+activemq:foo
+-----------
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+== Examples
+
+You'll need to provide a connectionFactory to the ActiveMQ Component, to have the following examples working.
+
+=== Producer Example
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("timer:mytimer?period=5000")
+    .setBody(constant("HELLO from Camel!"))
+    .to("activemq6:queue:HELLO.WORLD");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="timer:mytimer?period=5000"/>
+  <setBody>
+    <constant>HELLO from Camel!</constant>
+  </setBody>
+  <to uri="activemq6:queue:HELLO.WORLD"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: timer:mytimer
+      parameters:
+        period: 5000
+      steps:
+        - setBody:
+            constant: "HELLO from Camel!"
+        - to:
+            uri: activemq6:queue:HELLO.WORLD
+----
+====
+
+=== Consumer Example
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("activemq6:queue:HELLO.WORLD")
+    .log("Received a message - ${body}");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="activemq6:queue:HELLO.WORLD"/>
+  <log message="Received a message - ${body}"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: activemq6:queue:HELLO.WORLD
+      steps:
+        - log:
+            message: "Received a message - ${body}"
+----
+====
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aggregate-eip.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aggregate-eip.adoc
new file mode 100644
index 000000000000..28333acef8f5
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aggregate-eip.adoc
@@ -0,0 +1,816 @@
+= Aggregate EIP
+:doctitle: Aggregate
+:shortname: aggregate
+:description: Aggregates many messages into a single message
+:since: 
+:supportlevel: Stable
+:tabs-sync-option:
+
+The
+http://www.enterpriseintegrationpatterns.com/Aggregator.html[Aggregator]
+from the xref:enterprise-integration-patterns.adoc[EIP patterns] allows
+you to combine a number of messages into a single message.
+
+How do we combine the results of individual, but related, messages so that they can be processed as a whole?
+
+image::eip/Aggregator.gif[image]
+
+Use a stateful filter, an Aggregator, to collect and store individual messages until a complete set of related messages has been received. Then, the Aggregator publishes a single message distilled from the individual messages.
+
+The aggregator is one of the most complex EIP and has many features and configurations.
+
+The logic for combing messages together is _correlated_ in buckets based on a _correlation key_.
+Messages with the same correlation key are aggregated together, using an `AggregationStrategy`.
+
+== Aggregate options
+
+// eip options: START
+include::partial$eip-options.adoc[]
+// eip options: END
+
+== Exchange properties
+
+// eip exchangeProperties: START
+include::partial$eip-exchangeProperties.adoc[]
+// eip exchangeProperties: END
+
+== Worker pools
+
+The aggregate EIP will always use a worker pool used to process all the outgoing messages from the aggregator.
+The worker pool is determined accordingly:
+
+- If a custom `ExecutorService` has been configured, then this is used as worker pool.
+- If `parallelProcessing=true` then a _default_ worker pool (is 10 worker threads by default) is created.
+However, the thread pool size and other configurations can be configured using _thread pool profiles_.
+- Otherwise, a single threaded worker pool is created.
+- To achieve synchronous aggregation, use an instance of `SynchronousExecutorService` for the
+`executorService` option. The aggregated output will execute in the same thread that called the aggregator.
+
+== Aggregating
+
+The `AggregationStrategy` is used for aggregating the old, and the new exchanges together into a single exchange;
+that becomes the next old, when the next message is aggregated, and so forth.
+
+Possible implementations include performing some kind of combining or
+delta processing.
+For instance, adding line items together into an invoice or
+just using the newest exchange and removing old exchanges such as for
+state tracking or market data prices, where old values are of little
+use.
+
+Notice the aggregation strategy is a mandatory option and must be
+provided to the aggregator.
+
+IMPORTANT: In the aggregate method, do not create a new exchange instance to return,
+instead return either the old or new exchange from the input parameters;
+favor returning the old exchange whenever possible.
+
+Here are a few example `AggregationStrategy` implementations that should
+help you create your own custom strategy.
+
+._Java-only: example AggregationStrategy implementations_
+[source,java]
+----
+//simply combines Exchange String body values using '+' as a delimiter
+class StringAggregationStrategy implements AggregationStrategy {
+
+    public Exchange aggregate(Exchange oldExchange, Exchange newExchange) {
+        if (oldExchange == null) {
+            return newExchange;
+        }
+
+        String oldBody = oldExchange.getIn().getBody(String.class);
+        String newBody = newExchange.getIn().getBody(String.class);
+        oldExchange.getIn().setBody(oldBody + "+" + newBody);
+        return oldExchange;
+    }
+}
+
+//simply combines Exchange body values into an ArrayList<Object>
+class ArrayListAggregationStrategy implements AggregationStrategy {
+
+    public Exchange aggregate(Exchange oldExchange, Exchange newExchange) {
+        Object newBody = newExchange.getIn().getBody();
+        ArrayList<Object> list = null;
+        if (oldExchange == null) {
+            list = new ArrayList<Object>();
+            list.add(newBody);
+            newExchange.getIn().setBody(list);
+            return newExchange;
+        } else {
+            list = oldExchange.getIn().getBody(ArrayList.class);
+            list.add(newBody);
+            return oldExchange;
+        }
+    }
+}
+----
+
+TIP: The `org.apache.camel.builder.AggregationStrategies` is a builder that can
+be used for creating commonly used aggregation strategies without having to create a class.
+
+=== Aggregate by grouping exchanges
+
+In the route below we group all the exchanges together using
+`GroupedExchangeAggregationStrategy`:
+
+._Java-only: using GroupedExchangeAggregationStrategy_
+[source,java]
+----
+from("direct:start")
+    // aggregates all using the same expression and group the
+    // exchanges, so we get one single exchange containing all
+    // the others
+    .aggregate(new GroupedExchangeAggregationStrategy()).constant(true)
+    // wait for 0.5 seconds to aggregate
+    .completionTimeout(500L).to("mock:result");
+----
+
+As a result we have one outgoing `Exchange` being
+routed to the `"mock:result"` endpoint. The exchange is a holder
+containing all the incoming Exchanges.
+
+The output of the aggregator will then contain the exchanges grouped
+together in a list as shown below:
+
+._Java-only: retrieving grouped exchanges from message body_
+[source,java]
+----
+List<Exchange> grouped = exchange.getMessage().getBody(List.class);
+----
+
+=== Aggregating into a List
+
+If you want to aggregate some value from the messages `<V>` into a `List<V>`
+then you can use the
+`org.apache.camel.processor.aggregate.AbstractListAggregationStrategy`
+abstract class.
+
+The completed Exchange sent out of the aggregator will contain the `List<V>` in
+the message body.
+
+For example, to aggregate a `List<Integer>` you can extend this class as
+shown below, and implement the `getValue` method:
+
+._Java-only: extending AbstractListAggregationStrategy_
+[source,java]
+----
+public class MyListOfNumbersStrategy extends AbstractListAggregationStrategy<Integer> {
+
+    @Override
+    public Integer getValue(Exchange exchange) {
+        // the message body contains a number, so return that as-is
+        return exchange.getIn().getBody(Integer.class);
+    }
+}
+----
+
+The `org.apache.camel.builder.AggregationStrategies` is a builder that can
+be used for creating commonly used aggregation strategies without having to create a class.
+
+The previous example can also be built using the builder as shown:
+
+._Java-only: using AggregationStrategies builder_
+[source,java]
+----
+AggregationStrategy agg = AggregationStrategies.flexible(Integer.class)
+    .accumulateInCollection(ArrayList.class)
+    .pick(body());
+----
+
+=== Aggregating on timeout
+
+Camel invokes the `timeout` method on `AggregationStrategy` when the timeout occurs.
+Notice that the values for index and
+total parameters will be -1, and the timeout parameter will be provided
+only if configured as a fixed value. You must *not* throw any exceptions
+from the `timeout` method.
+
+=== Aggregate with persistent repository
+
+The aggregator provides a pluggable repository which you can implement
+your own `org.apache.camel.spi.AggregationRepository`.
+
+If you need a persistent repository, then Camel provides numerous implementations, such as from the
+xref:ROOT:caffeine-cache-component.adoc[Caffeine],
+xref:ROOT:cql-component.adoc[CassandraQL],
+xref:ROOT:ehcache-component.adoc[EHCache],
+xref:ROOT:infinispan-component.adoc[Infinispan],
+xref:ROOT:jcache-component.adoc[JCache],
+xref:others:leveldb.adoc[LevelDB],
+xref:others:redis.adoc[Redis],
+or xref:ROOT:sql-component.adoc[SQL] components.
+
+== Completion
+
+When aggregation xref:manual::exchange.adoc[Exchange]s at some point, you need to
+indicate that the aggregated exchanges are complete, so they can be sent
+out of the aggregator. Camel allows you to indicate completion in
+various ways as follows:
+
+* _completionTimeout_: Is an inactivity timeout in that is triggered if
+no new exchanges have been aggregated for that particular correlation
+key within the period.
+* _completionInterval_: Once every X period all the current aggregated
+exchanges are completed.
+* _completionSize_: Is a number indicating that after X aggregated
+exchanges its complete.
+* _completionPredicate_: Runs a xref:manual::predicate.adoc[Predicate] when a new
+exchange is aggregated to determine if we are complete or not.
+The configured aggregationStrategy can implement the
+Predicate interface and will be used as the completionPredicate if no
+completionPredicate is configured. The configured aggregationStrategy can
+override the `preComplete` method and will be used as
+the completionPredicate in pre-complete check mode. See further below
+for more details.
+* _completionFromBatchConsumer_: Special option for
+xref:manual::batch-consumer.adoc[Batch Consumer], which allows you to complete
+when all the messages from the batch have been aggregated.
+* _forceCompletionOnStop_: Indicates to complete all current
+aggregated exchanges when the context is stopped
+* _AggregateController_: which allows to use an external source (`AggregateController` implementation) to complete groups or all groups.
+This can be done using Java or JMX API.
+
+All the different completions are per correlation key. You can
+combine them in any way you like. It's basically the first that
+triggers that wins. So you can use a completion size together with a
+completion timeout. Only completionTimeout and completionInterval cannot
+be used at the same time.
+
+Completion is mandatory and must be configured on the aggregation.
+
+=== Pre-completion mode
+
+There can be use-cases where you want the incoming
+xref:manual::exchange.adoc[Exchange] to determine if the correlation group
+should pre-complete, and then the incoming
+xref:manual::exchange.adoc[Exchange] is starting a new group from scratch.
+The pre-completion mode must be enabled by the `AggregationStrategy` by overriding the `canPreComplete` method
+to return a `true` value.
+
+When pre-completion is enabled then the `preComplete` method is invoked:
+
+._Java-only: preComplete method signature_
+[source,java]
+----
+/**
+ * Determines if the aggregation should complete the current group, and start a new group, or the aggregation
+ * should continue using the current group.
+ *
+ * @param oldExchange the oldest exchange (is <tt>null</tt> on first aggregation as we only have the new exchange)
+ * @param newExchange the newest exchange (can be <tt>null</tt> if there was no data possible to acquire)
+ * @return <tt>true</tt> to complete current group and start a new group, or <tt>false</tt> to keep using current
+ */
+boolean preComplete(Exchange oldExchange, Exchange newExchange);
+----
+
+If the `preComplete` method returns `true`, then the existing correlation group is
+completed (without aggregating the incoming exchange (`newExchange`).
+Then the `newExchange` is used to start the correlation group from scratch,
+so the group would contain only that new incoming exchange. This is
+known as pre-completion mode.
+
+The `newExchange` contains the following exchange properties, which can be used
+to determine whether to pre complete.
+
+[width="100%",cols="3,1m,6",options="header"]
+|=======================================================================
+| Property | Type | Description
+| `CamelAggregatedSize` | `int` | The total number of messages aggregated.
+| `CamelAggregatedCorrelationKey` | `String` | The correlation identifier as a `String`.
+|=======================================================================
+
+When the aggregation is in _pre-completion_ mode, then only the following completions are in use:
+
+* _completionTimeout_ or _completionInterval_ can also be used as fallback
+completions
+* any other completions are not used (such as by size, from batch consumer, etc.)
+* _eagerCheckCompletion_ is implied as `true`, but the option has no effect
+
+=== Completion AggregationStrategy
+
+Camel invokes the `onComplete` on `AggregationStrategy` method when the aggregated `Exchange` is completed. This
+allows you to do any last minute custom logic such as to clean up some
+resources, or additional work on the exchange as it's now completed.
+You must *not* throw any exceptions from the `onCompletion` method.
+
+=== Completing the current group decided from the AggregationStrategy
+
+The `AggregationStrategy` supports checking for the exchange property (`Exchange.AGGREGATION_COMPLETE_CURRENT_GROUP`)
+on the returned `Exchange` that contains a boolean to indicate if the current
+group should be completed. This allows to overrule any existing
+completion predicates / sizes / timeouts etc., and complete the group.
+
+For example, the following logic will complete the
+group if the message body size is larger than 5. This is done by setting
+the exchange property `Exchange.AGGREGATION_COMPLETE_CURRENT_GROUP` to `true`.
+
+._Java-only: completing current group from AggregationStrategy_
+[source,java]
+----
+public final class MyCompletionStrategy implements AggregationStrategy {
+    @Override
+    public Exchange aggregate(Exchange oldExchange, Exchange newExchange) {
+        if (oldExchange == null) {
+            return newExchange;
+        }
+        String body = oldExchange.getIn().getBody(String.class) + "+"
+            + newExchange.getIn().getBody(String.class);
+        oldExchange.getIn().setBody(body);
+        if (body.length() >= 5) {
+            oldExchange.setProperty(Exchange.AGGREGATION_COMPLETE_CURRENT_GROUP, true);
+        }
+        return oldExchange;
+    }
+}
+----
+
+=== Completing all previous group decided from the AggregationStrategy
+
+The `AggregationStrategy` checks an exchange property, from the returned exchange,
+indicating if all previous groups should be completed.
+
+This allows to overrule any existing
+completion predicates / sizes / timeouts etc., and complete all the existing
+previous group.
+
+The following logic will complete all the
+previous groups, and start a new aggregation group.
+
+This is done by setting the property `Exchange.AGGREGATION_COMPLETE_ALL_GROUPS` to `true`
+on the returned exchange.
+
+._Java-only: completing all previous groups from AggregationStrategy_
+[source,java]
+----
+public final class MyCompletionStrategy implements AggregationStrategy {
+    @Override
+    public Exchange aggregate(Exchange oldExchange, Exchange newExchange) {
+        if (oldExchange == null) {
+            // we start a new correlation group, so complete all previous groups
+            newExchange.setProperty(Exchange.AGGREGATION_COMPLETE_ALL_GROUPS, true);
+            return newExchange;
+        }
+
+        String body1 = oldExchange.getIn().getBody(String.class);
+        String body2 = newExchange.getIn().getBody(String.class);
+
+        oldExchange.getIn().setBody(body1 + body2);
+        return oldExchange;
+    }
+}
+----
+
+=== Manually force the completion of all aggregated Exchanges immediately
+
+You can manually trigger completion of all current aggregated exchanges
+by sending an exchange containing the exchange property
+`Exchange.AGGREGATION_COMPLETE_ALL_GROUPS` set to `true`. The message is
+considered a signal message only, the message headers/contents will not
+be processed otherwise.
+
+You can alternatively set the exchange property
+`Exchange.AGGREGATION_COMPLETE_ALL_GROUPS_INCLUSIVE` to `true` to trigger
+completion of all groups after processing the current message.
+
+=== Using a controller to force the aggregator to complete
+
+The `org.apache.camel.processor.aggregate.AggregateController` allows
+you to control the aggregate at runtime using Java or JMX API. This can
+be used to force completing groups of exchanges, or query its current
+runtime statistics.
+
+The aggregator provides a default implementation if no custom one has been
+configured, which can be accessed using `getAggregateController()` method.
+Though it may be easier to configure a controller in the route using
+`aggregateController` as shown below:
+
+[tabs]
+====
+
+Java::
++
+[source,java]
+----
+private AggregateController controller = new DefaultAggregateController();
+
+from("direct:start")
+   .aggregate(header("id"), new MyAggregationStrategy())
+      .completionSize(10).id("myAggregator")
+      .aggregateController(controller)
+      .to("mock:aggregated");
+----
+
+XML::
++
+[source,xml]
+----
+<bean id="myController" class="org.apache.camel.processor.aggregate.DefaultAggregateController"/>
+
+<camelContext xmlns="http://camel.apache.org/schema/spring">
+    <route>
+        <from uri="direct:start"/>
+        <aggregate aggregationStrategy="myAppender" completionSize="10"
+                   aggregateController="myController">
+            <correlationExpression>
+                <header>id</header>
+            </correlationExpression>
+            <to uri="mock:result"/>
+        </aggregate>
+    </route>
+</camelContext>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:start
+      steps:
+        - aggregate:
+            aggregateController: myController
+            aggregationStrategy: myAppender
+            completionSize: 10
+            correlationExpression:
+              header:
+                expression: id
+            steps:
+              - to:
+                  uri: mock:result
+----
+====
+
+Then there is API on `AggregateController` to force completion. For
+example, to complete a group with key foo:
+
+._Java-only: forcing completion of a group via AggregateController_
+[source,java]
+----
+int groups = controller.forceCompletionOfGroup("foo");
+----
+
+The returned value is the number of groups completed.
+A value of 1 is returned if the foo group existed, otherwise 0 is returned.
+
+There is also a method to complete all groups:
+
+._Java-only: forcing completion of all groups_
+[source,java]
+----
+int groups = controller.forceCompletionOfAllGroups();
+----
+
+There is also JMX API on the aggregator which is available under the processors node in the Camel JMX tree.
+
+== Aggregating with Beans
+
+To use the `AggregationStrategy` you had to implement the
+`org.apache.camel.AggregationStrategy` interface,
+which means your logic would be tied to the Camel API.
+You can use a bean for the logic and let Camel adapt to your
+bean. To use a bean, then a convention must be followed:
+
+* there must be a public method to use
+* the method must not be void
+* the method can be static or non-static
+* the method must have two or more parameters
+* the parameters are paired, so the first half is applied to the
+`oldExchange`, and the reminder half is for the `newExchange`.
+ Therefore, there must be an equal number of parameters, e.g., 2, 4, 6, etc.
+
+The paired methods are expected to be ordered as follows:
+
+* the first parameter is the message body
+* optional, the second parameter is a `Map` of the headers
+* optional, the third parameter is a `Map` of the exchange properties
+
+This convention is best explained with some examples.
+
+In the method below, we have only two parameters, so the first parameter is
+the body of the `oldExchange`, and the second is paired to the body of the
+`newExchange`:
+
+._Java-only: bean method with two parameters_
+[source,java]
+----
+public String append(String existing, String next) {
+    return existing + next;
+}
+----
+
+In the method below, we have only four parameters, so the first parameter is
+the body of the `oldExchange`, and the second is the `Map` of the
+`oldExchange` headers, and the third is paired to the body of the `newExchange`,
+and the fourth parameter is the `Map` of the `newExchange` headers:
+
+._Java-only: bean method with four parameters_
+[source,java]
+----
+public String append(String existing, Map existingHeaders, String next, Map nextHeaders) {
+    return existing + next;
+}
+----
+
+And finally, if we have six parameters, that includes the exchange properties:
+
+._Java-only: bean method with six parameters_
+[source,java]
+----
+public String append(String existing, Map existingHeaders, Map existingProperties,
+                     String next, Map nextHeaders, Map nextProperties) {
+    return existing + next;
+}
+----
+
+To use this with the aggregate EIP, we can use a bean with the aggregate logic as follows:
+
+._Java-only: bean class for aggregation_
+[source,java]
+----
+public class MyBodyAppender {
+
+    public String append(String existing, String next) {
+        return next + existing;
+    }
+
+}
+----
+
+And then in the Camel route we create an instance of our bean, and then
+refer to the bean in the route using `bean` method from
+`org.apache.camel.builder.AggregationStrategies` as shown:
+
+[tabs]
+====
+
+Java::
++
+[source,java]
+----
+private MyBodyAppender appender = new MyBodyAppender();
+
+public void configure() throws Exception {
+    from("direct:start")
+        .aggregate(constant(true), AggregationStrategies.bean(appender, "append"))
+            .completionSize(3)
+            .to("mock:result");
+}
+----
+
+XML::
++
+[source,xml]
+----
+<bean id="myAppender" class="com.foo.MyBodyAppender"/>
+
+<camelContext xmlns="http://camel.apache.org/schema/spring">
+    <route>
+        <from uri="direct:start"/>
+        <aggregate aggregationStrategy="myAppender" aggregationStrategyMethodName="append" completionSize="3">
+            <correlationExpression>
+                <constant>true</constant>
+            </correlationExpression>
+            <to uri="mock:result"/>
+        </aggregate>
+    </route>
+</camelContext>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:start
+      steps:
+        - aggregate:
+            aggregationStrategy: myAppender
+            aggregationStrategyMethodName: append
+            completionSize: 3
+            correlationExpression:
+              constant:
+                expression: "true"
+            steps:
+              - to:
+                  uri: mock:result
+----
+====
+
+In Java DSL, you can also provide the bean class type directly:
+
+._Java-only: using AggregationStrategies.bean with class type_
+[source,java]
+----
+public void configure() throws Exception {
+    from("direct:start")
+        .aggregate(constant(true), AggregationStrategies.bean(MyBodyAppender.class, "append"))
+            .completionSize(3)
+            .to("mock:result");
+}
+----
+
+And if the bean has only one method, we do not need to specify the name
+of the method:
+
+._Java-only: using AggregationStrategies.bean without method name_
+[source,java]
+----
+public void configure() throws Exception {
+    from("direct:start")
+        .aggregate(constant(true), AggregationStrategies.bean(MyBodyAppender.class))
+            .completionSize(3)
+            .to("mock:result");
+}
+----
+
+And the `append` method could be static:
+
+._Java-only: bean class with static method_
+[source,java]
+----
+public class MyBodyAppender {
+
+    public static String append(String existing, String next) {
+        return next + existing;
+    }
+
+}
+----
+
+When using XML or YAML DSL, you can also specify the bean class directly in `aggregationStrategy`
+using the `#class:` syntax as shown:
+
+[tabs]
+====
+
+XML::
++
+[source,xml]
+----
+<route>
+    <from uri="direct:start"/>
+    <aggregate aggregationStrategy="#class:com.foo.MyBodyAppender" aggregationStrategyMethodName="append" completionSize="3">
+        <correlationExpression>
+            <constant>true</constant>
+        </correlationExpression>
+        <to uri="mock:result"/>
+    </aggregate>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:start
+      steps:
+        - aggregate:
+            aggregationStrategy: "#class:com.foo.MyBodyAppender"
+            aggregationStrategyMethodName: append
+            completionSize: 3
+            correlationExpression:
+              constant:
+                expression: "true"
+            steps:
+              - to:
+                  uri: mock:result
+----
+====
+
+=== Aggregating when no data
+
+When using bean as `AggregationStrategy`, then the method is
+*only* invoked when there is data to be aggregated, meaning that the message body
+is not `null`. In cases where you want to have the method invoked, even when there are no data (message body is `null`),
+then set the `strategyMethodAllowNull` to `true`.
+
+When using beans, this can be configured a bit easier using the `beanAllowNull` method
+from `AggregationStrategies` as shown:
+
+._Java-only: using AggregationStrategies.beanAllowNull_
+[source,java]
+----
+public void configure() throws Exception {
+    from("direct:start")
+        .pollEnrich("seda:foo", 1000, AggregationStrategies.beanAllowNull(appender, "append"))
+            .to("mock:result");
+}
+----
+
+Then the `append` method in the bean would need to deal with the
+situation that `newExchange` can be `null`:
+
+._Java-only: bean class handling null values_
+[source,java]
+----
+public class MyBodyAppender {
+
+    public String append(String existing, String next) {
+        if (next == null) {
+            return "NewWasNull" + existing;
+        } else {
+            return existing + next;
+        }
+    }
+
+}
+----
+
+In the example above we use the xref:content-enricher.adoc[Content Enricher]
+EIP using `pollEnrich`. The `newExchange` will be `null` in the
+situation we could not get any data from the "seda:foo" endpoint, and
+a timeout was hit after 1 second.
+
+So if we need to do special merge logic, we would need to set `setAllowNullNewExchange=true`.
+If we didn't do this, then on timeout the append method would normally not be
+invoked, meaning the xref:content-enricher.adoc[Content Enricher] did
+not merge/change the message.
+
+In XML and YAML DSL you would configure the `strategyMethodAllowNull` option and
+set it to `true` as shown below:
+
+[tabs]
+====
+
+XML::
++
+[source,xml]
+----
+<camelContext xmlns="http://camel.apache.org/schema/spring">
+    <route>
+        <from uri="direct:start"/>
+        <aggregate aggregationStrategy="myAppender"
+                   aggregationStrategyMethodName="append"
+                   aggregationStrategyMethodAllowNull="true"
+                   completionSize="3">
+            <correlationExpression>
+                <constant>true</constant>
+            </correlationExpression>
+            <to uri="mock:result"/>
+        </aggregate>
+    </route>
+</camelContext>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:start
+      steps:
+        - aggregate:
+            aggregationStrategy: myAppender
+            aggregationStrategyMethodName: append
+            aggregationStrategyMethodAllowNull: true
+            completionSize: 3
+            correlationExpression:
+              constant:
+                expression: "true"
+            steps:
+              - to:
+                  uri: mock:result
+----
+====
+
+=== Aggregating with different body types
+
+When, for example, using `strategyMethodAllowNull` as `true`, then the
+parameter type of the message bodies does not have to be the same.
+For example suppose we want to aggregate from a `com.foo.User` type to a
+`List<String>` that contains the name of the user. We could code a bean as follows:
+
+._Java-only: bean class aggregating different body types_
+[source,java]
+----
+public final class MyUserAppender {
+
+    public List addUsers(List names, User user) {
+        if (names == null) {
+            names = new ArrayList();
+        }
+        names.add(user.getName());
+        return names;
+    }
+}
+----
+
+Notice that the return type is a `List` which we want to contain the name of the users.
+The first parameter is the `List` of names, and the second parameter is the incoming `com.foo.User` type.
+
+=== Aggregating after large split
+
+If you use the xref:split-eip.adoc[Split] EIP before this aggregator then beware that if you
+use a completion condition, such as `completionSize(1)`, then this can lead to the current thread
+being over utilized and its thread-stack becoming very large. This can cause the JVM to throw `StackOverflowException`.
+
+The reason is that the same thread is both doing the large split, the aggregation, and also the completion
+of the aggregator all in the same thread. This can lead to deep thread-stacks. To avoid this,
+you can ensure the aggregator uses a different thread to process the completion routing, by enabling `parallelProcessing(true)`.
+
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ai-patterns.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ai-patterns.adoc
new file mode 100644
index 000000000000..a783c5882f69
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ai-patterns.adoc
@@ -0,0 +1,218 @@
+= AI Patterns
+:doctitle: AI Patterns
+:shortname: ai-patterns
+:description: Common AI and modern software design pattern terms mapped to Camel EIPs
+
+If you come from an AI, data engineering, or modern distributed systems background,
+you may know integration patterns by different names. This page maps common
+terms to the corresponding Camel EIPs.
+
+See also the full xref:enterprise-integration-patterns.adoc[Enterprise Integration Patterns] index.
+
+== Data Flow
+
+[width="100%",cols="20%,30%,50%"]
+|===
+|Term |Camel EIP |Description
+
+|Pipeline / Chain
+|xref:pipeline-eip.adoc[Pipes and Filters]
+|Process a message through a sequence of steps.
+
+|Fan-out / Broadcast
+|xref:multicast-eip.adoc[Multicast]
+|Send the same message to multiple destinations in parallel.
+
+|Fan-in / Reduce / Join
+|xref:aggregate-eip.adoc[Aggregator]
+|Combine multiple related messages into a single message.
+
+|Scatter-Gather
+|xref:scatter-gather.adoc[Scatter-Gather]
+|Send a message to multiple recipients and aggregate their replies.
+
+|Map / Transform
+|xref:transform-eip.adoc[Transform], xref:setBody-eip.adoc[Set Body]
+|Transform or replace the message content.
+
+|Split / Chunk
+|xref:split-eip.adoc[Splitter]
+|Break a message into smaller pieces for individual processing.
+
+|Merge
+|xref:aggregate-eip.adoc[Aggregator]
+|Merge multiple messages into one using a correlation key and aggregation strategy.
+
+|Filter
+|xref:filter-eip.adoc[Message Filter]
+|Discard messages that do not match a predicate.
+
+|Router / Dispatch
+|xref:choice-eip.adoc[Content-Based Router], xref:dynamicRouter-eip.adoc[Dynamic Router]
+|Route messages to different destinations based on content or rules.
+|===
+
+== Enrichment and Context
+
+[width="100%",cols="20%,30%,50%"]
+|===
+|Term |Camel EIP |Description
+
+|Enrich / Hydrate / Augment
+|xref:enrich-eip.adoc[Enrich], xref:pollEnrich-eip.adoc[Poll Enrich]
+|Fetch additional data from an external source and merge it into the message.
+
+|Validate / Guard
+|xref:validate-eip.adoc[Validate]
+|Check that a message satisfies a condition before further processing.
+
+|Normalize
+|xref:normalizer.adoc[Normalizer]
+|Convert messages from different formats into a single canonical format.
+
+|Serialize / Deserialize
+|xref:marshal-eip.adoc[Marshal], xref:unmarshal-eip.adoc[Unmarshal]
+|Convert between objects and wire formats (JSON, XML, Avro, Protobuf, etc.).
+|===
+
+== Resilience and Error Handling
+
+[width="100%",cols="20%,30%,50%"]
+|===
+|Term |Camel EIP |Description
+
+|Retry
+|xref:manual::error-handler.adoc[Error Handler]
+|Automatically retry failed message processing with configurable backoff.
+
+|Circuit Breaker
+|xref:circuitBreaker-eip.adoc[Circuit Breaker]
+|Stop calling a failing service and provide a fallback response.
+
+|Fallback
+|xref:manual::exception-clause.adoc[On Exception], xref:onFallback-eip.adoc[On Fallback]
+|Handle exceptions with onException (general), or define a Circuit Breaker fallback with onFallback.
+
+|Dead Letter / Poison Pill
+|xref:dead-letter-channel.adoc[Dead Letter Channel]
+|Move messages that cannot be processed to a separate channel for investigation.
+
+|Compensate / Rollback
+|xref:saga-eip.adoc[Saga], xref:rollback-eip.adoc[Rollback]
+|Undo or compensate for completed steps when a multi-step process fails.
+|===
+
+== Rate Control and Scheduling
+
+[width="100%",cols="20%,30%,50%"]
+|===
+|Term |Camel EIP |Description
+
+|Rate Limit / Throttle
+|xref:throttle-eip.adoc[Throttler]
+|Limit the number of messages processed per time period.
+
+|Debounce / Delay
+|xref:delay-eip.adoc[Delayer]
+|Introduce a delay before processing a message.
+
+|Poll / Pull
+|xref:polling-consumer.adoc[Polling Consumer], xref:poll-eip.adoc[Poll]
+|Consume messages on demand rather than being pushed.
+
+|Loop / Iterate
+|xref:loop-eip.adoc[Loop]
+|Repeat processing a message a fixed number of times or until a condition is met.
+
+|Sample
+|xref:sample-eip.adoc[Sampling]
+|Pick one message out of many in a time period to reduce volume.
+|===
+
+== Load Distribution
+
+[width="100%",cols="20%,30%,50%"]
+|===
+|Term |Camel EIP |Description
+
+|Load Balance
+|xref:loadBalance-eip.adoc[Load Balancer]
+|Distribute messages across multiple endpoints.
+
+|Round Robin
+|xref:roundRobinLoadBalancer-eip.adoc[Round Robin Load Balancer]
+|Distribute messages evenly in rotation.
+
+|Failover
+|xref:failoverLoadBalancer-eip.adoc[Failover Load Balancer]
+|Try the next endpoint when the current one fails.
+
+|Weighted
+|xref:weightedLoadBalancer-eip.adoc[Weighted Load Balancer]
+|Distribute messages according to weighted ratios.
+
+|Sticky / Affinity
+|xref:stickyLoadBalancer-eip.adoc[Sticky Load Balancer]
+|Route related messages to the same endpoint based on a correlation key.
+|===
+
+== Deduplication and Idempotency
+
+[width="100%",cols="20%,30%,50%"]
+|===
+|Term |Camel EIP |Description
+
+|Dedup / Deduplicate
+|xref:idempotentConsumer-eip.adoc[Idempotent Consumer]
+|Detect and discard duplicate messages based on a unique identifier.
+
+|Claim Check / Stash
+|xref:claimCheck-eip.adoc[Claim Check]
+|Temporarily store message data and retrieve it later to reduce payload size.
+|===
+
+== Connectivity
+
+[width="100%",cols="20%,30%,50%"]
+|===
+|Term |Camel EIP |Description
+
+|Source / Ingress
+|xref:from-eip.adoc[From]
+|Define the input endpoint that feeds messages into a route.
+
+|Sink / Egress
+|xref:to-eip.adoc[To], xref:toD-eip.adoc[To D]
+|Send messages to a fixed or dynamically computed endpoint.
+
+|Connector / Adapter
+|xref:channel-adapter.adoc[Channel Adapter]
+|Connect an application to a messaging system.
+
+|Webhook / Event-Driven
+|xref:eventDrivenConsumer-eip.adoc[Event Driven Consumer]
+|React to messages as they arrive without polling.
+
+|Gateway
+|xref:messaging-gateway.adoc[Messaging Gateway]
+|Encapsulate access to the messaging system behind a clean interface.
+
+|Wire Tap / Tap / Observe
+|xref:wireTap-eip.adoc[Wire Tap]
+|Send a copy of the message to a secondary destination for monitoring.
+|===
+
+== AI and Agent Integration
+
+[width="100%",cols="20%,30%,50%"]
+|===
+|Term |Camel Component / EIP |Description
+
+|Agent-to-Agent / A2A
+|xref:ROOT:a2a-component.adoc[A2A]
+|Google's Agent-to-Agent protocol for communication between AI agents.
+
+|Tokenize / Chunk (for LLM)
+|xref:others:langchain4j-tokenizer.adoc[LangChain4j Tokenizer]
+|Split text into tokens or chunks sized for LLM context windows, using LangChain4j tokenizer strategies.
+|===
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ai-tool-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ai-tool-component.adoc
new file mode 100644
index 000000000000..e478e135d097
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ai-tool-component.adoc
@@ -0,0 +1,219 @@
+= AI Tool Component
+:doctitle: AI Tool
+:shortname: ai-tool
+:artifactid: camel-ai-tool
+:description: Framework-agnostic consumer endpoint that registers a Camel route as an LLM tool in the shared AiToolRegistry.
+:since: 4.22
+:supportlevel: Preview
+:tabs-sync-option:
+:component-header: Only consumer is supported
+//Manually maintained attributes
+:group: AI
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The AI Tool component exposes Camel routes as tools that AI models can call.
+Any AI producer component (such as xref:langchain4j-agent-component.adoc[LangChain4j Agent] or
+xref:spring-ai-chat-component.adoc[Spring AI Chat]) discovers registered tools using tag-based filtering.
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+[source,xml]
+----
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-ai-tool</artifactId>
+    <version>x.x.x</version>
+    <!-- use the same version as your Camel core version -->
+</dependency>
+----
+
+== URI format
+
+----
+ai-tool:toolName[?options]
+----
+
+Where *toolName* is the name the LLM sees and uses to invoke the tool.
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+== Usage
+
+=== Basic Tool Definition
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("ai-tool:weather?tags=weather&description=Get current weather for a city" +
+    "&parameter.city=string&parameter.city.description=The city name")
+    .to("bean:weatherService");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="ai-tool:weather?tags=weather&amp;description=Get current weather for a city&amp;parameter.city=string&amp;parameter.city.description=The city name"/>
+  <to uri="bean:weatherService"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: ai-tool:weather
+      parameters:
+        tags: weather
+        description: "Get current weather for a city"
+        parameter.city: string
+        parameter.city.description: "The city name"
+      steps:
+        - to:
+            uri: bean:weatherService
+----
+====
+
+=== Tool with Multiple Parameters
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("ai-tool:calculator?tags=math" +
+    "&description=Calculate a math expression" +
+    "&parameter.a=number" +
+    "&parameter.a.description=First operand" +
+    "&parameter.a.required=true" +
+    "&parameter.b=number" +
+    "&parameter.b.description=Second operand" +
+    "&parameter.b.required=true" +
+    "&parameter.operation=string" +
+    "&parameter.operation.description=The operation to perform" +
+    "&parameter.operation.enum=add,subtract,multiply,divide")
+    .to("direct:calculator");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="ai-tool:calculator?tags=math&amp;description=Calculate a math expression&amp;parameter.a=number&amp;parameter.a.description=First operand&amp;parameter.a.required=true&amp;parameter.b=number&amp;parameter.b.description=Second operand&amp;parameter.b.required=true&amp;parameter.operation=string&amp;parameter.operation.description=The operation to perform&amp;parameter.operation.enum=add,subtract,multiply,divide"/>
+  <to uri="direct:calculator"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: ai-tool:calculator
+      parameters:
+        tags: math
+        description: "Calculate a math expression"
+        parameter.a: number
+        parameter.a.description: "First operand"
+        parameter.a.required: true
+        parameter.b: number
+        parameter.b.description: "Second operand"
+        parameter.b.required: true
+        parameter.operation: string
+        parameter.operation.description: "The operation to perform"
+        parameter.operation.enum: "add,subtract,multiply,divide"
+      steps:
+        - to:
+            uri: direct:calculator
+----
+====
+
+=== Tag-Based Discovery
+
+Tags group tools so that AI producers can select relevant subsets.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+// Define tools with tags
+from("ai-tool:weather?tags=weather,external-api&description=Get weather for a city" +
+    "&parameter.city=string&parameter.city.description=The city name")
+    .to("bean:weatherService");
+
+from("ai-tool:lookupUser?tags=users&description=Look up a user by ID" +
+    "&parameter.id=integer&parameter.id.description=The user ID&parameter.id.required=true")
+    .to("bean:userService?method=findById(${header.id})");
+----
+
+XML::
++
+[source,xml]
+----
+<!-- Define tools with tags -->
+<route>
+  <from uri="ai-tool:weather?tags=weather,external-api&amp;description=Get weather for a city&amp;parameter.city=string&amp;parameter.city.description=The city name"/>
+  <to uri="bean:weatherService"/>
+</route>
+
+<route>
+  <from uri="ai-tool:lookupUser?tags=users&amp;description=Look up a user by ID&amp;parameter.id=integer&amp;parameter.id.description=The user ID&amp;parameter.id.required=true"/>
+  <to uri="bean:userService?method=findById(${header.id})"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+# Define tools with tags
+- route:
+    from:
+      uri: ai-tool:weather
+      parameters:
+        tags: weather,external-api
+        description: "Get weather for a city"
+        parameter.city: string
+        parameter.city.description: "The city name"
+      steps:
+        - to:
+            uri: bean:weatherService
+
+- route:
+    from:
+      uri: ai-tool:lookupUser
+      parameters:
+        tags: users
+        description: "Look up a user by ID"
+        parameter.id: integer
+        parameter.id.description: "The user ID"
+        parameter.id.required: true
+      steps:
+        - to:
+            uri: "bean:userService?method=findById(${header.id})"
+----
+====
+
+== See Also
+
+* xref:langchain4j-agent-component.adoc[LangChain4j Agent Component] — will discover ai-tool tools in a future release
+* xref:spring-ai-chat-component.adoc[Spring AI Chat Component] — will discover ai-tool tools in a future release
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/amqp-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/amqp-component.adoc
new file mode 100644
index 000000000000..2443855fc1bd
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/amqp-component.adoc
@@ -0,0 +1,161 @@
+= AMQP Component
+:doctitle: AMQP
+:shortname: amqp
+:artifactid: camel-amqp
+:description: Messaging with AMQP protocol using Apache Qpid Client.
+:since: 1.2
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Both producer and consumer are supported
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The AMQP component supports the
+http://www.amqp.org/[AMQP 1.0 protocol]
+using the JMS Client API of the http://qpid.apache.org/[Qpid]
+project.
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+[source,xml]
+----
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-amqp</artifactId>
+    <version>${camel.version}</version> <!-- use the same version as your Camel core version -->
+</dependency>
+----
+
+== URI format
+
+._Java-only: URI format syntax_
+[source,java]
+----
+amqp:[queue:|topic:]destinationName[?options]
+----
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+
+== Usage
+
+As AMQP component is inherited from JMS component, the usage of the
+former is almost identical to the latter:
+
+*Using AMQP component*
+
+._Java-only: Java DSL snippet (incomplete route)_
+[source,java]
+----
+// Consuming from AMQP queue
+from("amqp:queue:incoming").
+  to(...);
+
+// Sending messages to the AMQP topic
+from(...).
+  to("amqp:topic:notify");
+----
+
+== Configuring AMQP component
+
+*Creating AMQP 1.0 component*
+
+AMQPComponents may be created using the provided factory methods, for example:
+
+._Java-only: Java programmatic component factory_
+[source,java]
+----
+AMQPComponent amqp = AMQPComponent.amqpComponent("amqp://localhost:5672");
+
+AMQPComponent authorizedAmqp = AMQPComponent.amqpComponent("amqp://localhost:5672", "user", "password");
+----
+
+Alternatively, the AMQP Component can be initialized by providing one or more of the available options for
+configuring SSL, authentication, and AMQP Broker host and port.
+
+*SSL configuration*
+
+The component can be configured to connect to an AMQP broker using SSL by setting the
+`useSsl` option and providing keystore and truststore details, for example:
+
+._Java-only: Java programmatic SSL configuration_
+[source,java]
+----
+AMQPComponent component = new AMQPComponent();
+component.setUseSsl(true);
+component.setTrustStoreLocation(
+        getClass().getClassLoader().getResource("server-ca-truststore.p12").getFile());
+component.setTrustStorePassword("securepass");
+component.setTrustStoreType("PKCS12");
+component.setKeyStoreLocation(
+        getClass().getClassLoader().getResource("server-keystore.p12").getFile());
+component.setKeyStorePassword("securepass");
+component.setKeyStoreType("PKCS12");
+----
+
+*Authentication configuration*
+
+A username and password may be provided for AMQP broker authentication:
+
+._Java-only: Java programmatic component configuration_
+[source,java]
+----
+AMQPComponent component = new AMQPComponent();
+component.setUsername("camel");
+component.setPassword("rider");
+----
+
+*AMQP Broker host and port configuration*
+
+._Java-only: Java programmatic component configuration_
+[source,java]
+----
+AMQPComponent amqpComponent = new AMQPComponent();
+amqpComponent.setHost("remoteHost");
+amqpComponent.setPort(5555);
+----
+
+If `host` or `port` options have not been provided and the component is initialized using one or more of the other available
+options the host on the AMQP JMSConnectionFactory URI is set to 'localhost' if not provided, and the port is set to '5672'
+if not provided.
+
+
+*Enabling AMQP specific options*
+
+If you, for example, need to enable `amqp.traceFrames` you can do that by appending the option to your URI, like the following example:
+
+._Java-only: Java programmatic component factory_
+[source,java]
+----
+AMQPComponent amqp = AMQPComponent.amqpComponent("amqp://localhost:5672?amqp.traceFrames=true");
+----
+
+For reference, take a look at the https://qpid.apache.org/releases/qpid-jms-1.7.0/docs/index.html[QPID JMS client configuration]
+
+== Using topics
+
+To have using topics working with `camel-amqp` you need to configure the
+component to use `topic://` as topic prefix, as shown below:
+
+[source,xml]
+----
+ <bean id="amqp" class="org.apache.camel.component.amqp.AmqpComponent">
+   <property name="connectionFactory">
+     <bean class="org.apache.qpid.jms.JmsConnectionFactory" factory-method="createFromURL">
+       <property name="remoteURI" value="amqp://localhost:5672" />
+       <property name="topicPrefix" value="topic://" />  <!-- only necessary when connecting to ActiveMQ over AMQP 1.0 -->
+     </bean>
+   </property>
+ </bean>
+----
+
+
+Keep in mind that the factory methods `AMQPComponent#amqpComponent(String)` and `AMQPComponent#amqpComponent(String, String, String)` configure
+the Topic prefix as `topic://` by default, so you don't have to configure it explicitly.
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/arangodb-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/arangodb-component.adoc
new file mode 100644
index 000000000000..5c2f11e54c3a
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/arangodb-component.adoc
@@ -0,0 +1,143 @@
+= ArangoDb Component
+:doctitle: ArangoDb
+:shortname: arangodb
+:artifactid: camel-arangodb
+:description: Perform operations on ArangoDb when used as a Document Database, or as a Graph Database
+:since: 3.5
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Only producer is supported
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The ArangoDb component is client for ArangoDb that uses the https://github.com/arangodb/arangodb-java-driver[arango java driver] to perform queries on collections and graphs in the ArangoDb database.
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+[source,xml]
+----
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-arangodb</artifactId>
+    <version>x.x.x</version>
+  <!-- use the same version as your Camel core version -->
+</dependency>
+----
+
+
+== URI format
+
+----
+arangodb:database[?options]
+----
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+== Examples
+
+=== Producer Examples
+
+==== Save document on a collection
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:insert")
+    .to("arangodb:testDb?documentCollection=collection&operation=SAVE_DOCUMENT");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:insert"/>
+  <to uri="arangodb:testDb?documentCollection=collection&amp;operation=SAVE_DOCUMENT"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:insert
+      steps:
+        - to:
+            uri: arangodb:testDb
+            parameters:
+              documentCollection: collection
+              operation: SAVE_DOCUMENT
+----
+====
+
+And you can set as body a BaseDocument class 
+
+----
+BaseDocument myObject = new BaseDocument();
+myObject.addAttribute("a", "Foo");
+myObject.addAttribute("b", 42);
+----
+
+==== Query a collection
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:query")
+    .to("arangodb:testDb?operation=AQL_QUERY");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:query"/>
+  <to uri="arangodb:testDb?operation=AQL_QUERY"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:query
+      steps:
+        - to:
+            uri: arangodb:testDb
+            parameters:
+              operation: AQL_QUERY
+----
+====
+
+And you can invoke an AQL Query in this way
+
+._Java-only: ProducerTemplate with AQL query parameters and string concatenation_
+[source,java]
+----
+String query = "FOR t IN " + COLLECTION_NAME + " FILTER t.value == @value";
+Map<String, Object> bindVars = new MapBuilder().put("value", "hello")
+        .get();
+
+Exchange result = template.request("direct:query", exchange -> {
+    exchange.getMessage().setHeader(AQL_QUERY, query);
+    exchange.getMessage().setHeader(AQL_QUERY_BIND_PARAMETERS, bindVars);
+});
+----
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/as2-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/as2-component.adoc
new file mode 100644
index 000000000000..6ac5717c2cda
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/as2-component.adoc
@@ -0,0 +1,56 @@
+= AS2 Component
+:doctitle: AS2
+:shortname: as2
+:artifactid: camel-as2
+:description: Transfer data securely and reliably using the AS2 protocol (RFC4130).
+:since: 2.22
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Both producer and consumer are supported
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The AS2 component provides transport of EDI messages using the HTTP transfer protocol
+as specified in https://tools.ietf.org/html/rfc4130[RFC4130]. 
+
+Maven users will need to add the following dependency to their pom.xml
+for this component:
+
+[source,xml]
+----
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-as2</artifactId>
+    <version>x.x.x</version>
+    <!-- use the same version as your Camel core version -->
+</dependency>
+----
+
+== URI format
+
+----
+as2://apiName/methodName
+----
+
+apiName can be one of:
+
+* client
+* server
+
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+[NOTE]
+====
+This is an API-based component, so per-call parameters can be supplied through `Camel`-prefixed
+exchange headers in addition to the endpoint options. If the route consumes messages from untrusted
+producers, strip these internal headers at the trust boundary -- for example with
+`removeHeaders("Camel*")` -- before the message reaches this component, so that a sender cannot
+override the API call. See xref:manual::security-model.adoc[the Camel security model] for details.
+====
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/asn1-dataformat.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/asn1-dataformat.adoc
new file mode 100644
index 000000000000..28a8a0890847
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/asn1-dataformat.adoc
@@ -0,0 +1,81 @@
+= ASN.1 File DataFormat
+:doctitle: ASN.1 File
+:shortname: asn1
+:artifactid: camel-asn1
+:description: Encode and decode data structures using Abstract Syntax Notation One (ASN.1)
+:since: 2.20
+:supportlevel: Stable
+:tabs-sync-option:
+
+*Since Camel {since}*
+
+The https://www.itu.int/en/ITU-T/asn1/Pages/introduction.aspx[ASN.1 Data Format] is a Camel Framework's data format implementation based on Bouncy Castle's bcprov-jdk18on library and jASN.1's java compiler for the formal notation used for describing data transmitted by telecommunications protocols, regardless of language implementation and physical representation of these data, whatever the application, whether complex or very simple.
+Messages can be unmarshalled (conversion to simple Java POJO(s)) to plain Java objects.
+With the help of Camel's routing engine and data transformations, you can then play with POJO(s) and apply customized formatting and call other Camel Components to convert and send messages to upstream systems.
+
+== ASN.1 Data Format Options
+
+// dataformat options: START
+include::partial$dataformat-options.adoc[]
+// dataformat options: END
+
+== Unmarshal
+
+There are 3 different ways to unmarshal ASN.1 structured messages. (Usually binary files)
+
+In this first example, we unmarshal BER file payload to OutputStream and send it to mock endpoint.
+
+._Java-only: uses the asn1 data format object directly_
+[source,java]
+----
+from("direct:unmarshal").unmarshal(asn1).to("mock:unmarshal");
+----
+
+In the second example, we unmarshal BER file payload to a byte array using Split EIP.
+The reason for applying Split EIP is that usually each BER file or (ASN.1 structured file) contains multiple records to process and Split EIP helps us to get each record in a file as byte arrays which is actually ASN1Primitive's instance (by the use of Bouncy Castle's ASN.1 support in bcprov-jdk18on library)
+Byte arrays then may be converted to ASN1Primitive by the help of public static method in (ASN1Primitive.fromByteArray)
+In such example, note that you need to set `usingIterator=true`
+
+._Java-only: uses the asn1 data format object and Split EIP with bodyAs_
+[source,java]
+----
+from("direct:unmarshal")
+    .unmarshal(asn1)
+    .split(bodyAs(Iterator.class)).streaming()
+        .to("mock:unmarshal");
+----
+
+In the last example, we unmarshalled a BER file payload to plain old Java Objects using Split EIP. The reason for applying Split EIP is already mentioned in the previous example. Please note and keep in mind that reason. In such example we also need to set the fully qualified name of the class or <YourObject>.class reference through data format.
+The important thing to note here is that your object should have been generated by jasn1 compiler, which is a nice tool to generate java object representations of your ASN.1 structure.
+For the reference usage of jasn1 compiler, see the https://www.beanit.com/asn1/[JASN.1 Project Page] and please also see how the compiler is invoked with the help of maven's exec plugin.
+For example, in this data format's unit tests an example ASN.1 structure(TestSMSBerCdr.asn1) is added in `src/test/resources/asn1_structure`. jasn1 compiler is invoked, and java object's representations are generated in `$\{basedir}/target/generated/src/test/java`
+The nice thing about this example, you will get POJO instance at the mock endpoint or at whatever your endpoint is.
+
+._Java-only: uses unmarshal with class name and Split EIP with bodyAs_
+[source,java]
+----
+from("direct:unmarshaldsl")
+         .unmarshal()
+         .asn1("org.apache.camel.dataformat.asn1.model.testsmscbercdr.SmsCdr")
+         .split(bodyAs(Iterator.class)).streaming()
+            .to("mock:unmarshaldsl");
+----
+
+== Dependencies
+
+To use ASN.1 data format in your camel routes you need to add a dependency on
+*camel-asn1* which implements this data format.
+
+If you use Maven you can add the following to your `pom.xml`,
+substituting the version number for the latest & greatest release (see
+the download page for the latest versions).
+
+[source,xml]
+----
+<dependency>
+  <groupId>org.apache.camel</groupId>
+  <artifactId>camel-asn1</artifactId>
+  <version>x.x.x</version>
+  <!-- use the same version as your Camel core version -->
+</dependency>
+----
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/asterisk-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/asterisk-component.adoc
new file mode 100644
index 000000000000..5bb9ae53215f
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/asterisk-component.adoc
@@ -0,0 +1,131 @@
+= Asterisk Component
+:doctitle: Asterisk
+:shortname: asterisk
+:artifactid: camel-asterisk
+:description: Interact with Asterisk PBX Server (VoIP).
+:since: 2.18
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Both producer and consumer are supported
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The Asterisk component allows you to work easily with an Asterisk PBX Server http://www.asterisk.org/ using https://asterisk-java.org/[asterisk-java]
+
+This component helps to interface with http://www.voip-info.org/wiki-Asterisk+manager+API[Asterisk Manager Interface]
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+[source,xml]
+------------------------------------------------------------
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-asterisk</artifactId>
+    <version>x.x.x</version>
+    <!-- use the same version as your Camel core version -->
+</dependency>
+------------------------------------------------------------
+
+== URI format
+
+----
+asterisk:name[?options]
+----
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+== Action
+
+Supported actions are:
+
+* QUEUE_STATUS: Queue status
+* SIP_PEERS: List SIP peers
+* EXTENSION_STATE: Check extension status
+
+== Examples
+
+=== Producer Example
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:in")
+  .to("asterisk://myVoIP?hostname=hostname&username=username&password=password&action=EXTENSION_STATE");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:in"/>
+  <to uri="asterisk://myVoIP?hostname=hostname&amp;username=username&amp;password=password&amp;action=EXTENSION_STATE"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:in
+      steps:
+        - to:
+            uri: asterisk://myVoIP
+            parameters:
+              hostname: hostname
+              username: username
+              password: password
+              action: EXTENSION_STATE
+----
+====
+
+=== Consumer Example
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("asterisk:myVoIP?hostname=hostname&username=username&password=password")
+  .log("Received a message - ${body}");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="asterisk:myVoIP?hostname=hostname&amp;username=username&amp;password=password"/>
+  <log message="Received a message - ${body}"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: asterisk:myVoIP
+      parameters:
+        hostname: hostname
+        username: username
+        password: password
+      steps:
+        - log:
+            message: "Received a message - ${body}"
+----
+====
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/atmosphere-websocket-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/atmosphere-websocket-component.adoc
new file mode 100644
index 000000000000..2ba2242b6d68
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/atmosphere-websocket-component.adoc
@@ -0,0 +1,124 @@
+= Atmosphere Websocket Component
+:doctitle: Atmosphere Websocket
+:shortname: atmosphere-websocket
+:artifactid: camel-atmosphere-websocket
+:description: Expose WebSocket endpoints using the Atmosphere framework.
+:since: 2.14
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Both producer and consumer are supported
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The Atmosphere-Websocket component provides Websocket
+based endpoints for a servlet communicating with
+external clients over Websocket (as a servlet accepting websocket
+connections from external clients). This component uses
+the https://github.com/Atmosphere/atmosphere[Atmosphere] library to
+support the Websocket transport in various Servlet containers.
+
+Maven users will need to add the following dependency to
+their `pom.xml` for this component:
+
+[source,xml]
+------------------------------------------------------------
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-atmosphere-websocket</artifactId>
+    <version>x.x.x</version>
+    <!-- use the same version as your Camel core version -->
+</dependency>
+------------------------------------------------------------
+
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+== Reading and Writing Data over Websocket
+
+An atmopshere-websocket endpoint can either write data to the socket or
+read from the socket, depending on whether the endpoint is configured as
+the producer or the consumer, respectively.
+
+== Examples
+
+=== Consumer Example
+
+In the route below, Camel will read from the specified websocket
+connection.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("atmosphere-websocket:///servicepath")
+        .to("direct:next");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="atmosphere-websocket:///servicepath"/>
+  <to uri="direct:next"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: atmosphere-websocket:///servicepath
+      steps:
+        - to:
+            uri: direct:next
+----
+====
+
+=== Producer Example
+
+In the route below, Camel will write to the specified websocket
+connection.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:next")
+        .to("atmosphere-websocket:///servicepath");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:next"/>
+  <to uri="atmosphere-websocket:///servicepath"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:next
+      steps:
+        - to:
+            uri: atmosphere-websocket:///servicepath
+----
+====
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/atom-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/atom-component.adoc
new file mode 100644
index 000000000000..efe40c225a43
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/atom-component.adoc
@@ -0,0 +1,235 @@
+= Atom Component
+:doctitle: Atom
+:shortname: atom
+:artifactid: camel-atom
+:description: Poll Atom RSS feeds.
+:since: 1.2
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Only consumer is supported
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The Atom component is used for polling Atom feeds.
+
+Camel will poll the feed every 60 seconds by default. +
+ *Note:* The component currently only supports polling (consuming)
+feeds.
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+[source,xml]
+----
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-atom</artifactId>
+    <version>x.x.x</version>
+    <!-- use the same version as your Camel core version -->
+</dependency>
+----
+
+== URI format
+
+----
+atom://atomUri[?options]
+----
+
+Where *atomUri* is the URI to the Atom feed to poll.
+
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+
+== Exchange data format
+
+Camel will set the In body on the returned `Exchange` with the entries.
+Depending on the `splitEntries` flag Camel will either return one
+`Entry` or a `List<Entry>`.
+
+[width="100%",cols="10%,10%,80%",options="header",]
+|=======================================================================
+|Option |Value |Behavior
+|`splitEntries` |`true` |Only a single entry from the currently being processed feed is set:
+`exchange.in.body(Entry)`
+
+|`splitEntries` |`false` |The entire list of entries from the feed is set:
+`exchange.in.body(List<Entry>)`
+|=======================================================================
+
+Camel can set the `Feed` object on the In header (see `feedHeader`
+option to disable this):
+
+== Usage
+
+=== Avoid reading the same entry more than once (idempotent consumer)
+
+Camel supports Idempotent Consumer
+directly within the component, so it will skip already processed entries.
+This feature is enabled by default, but can be disabled by setting the `idempotent=false` option.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("file://inbox?idempotent=false").to("...");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="file://inbox?idempotent=false"/>
+  <to uri="..."/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: file://inbox
+      parameters:
+        idempotent: false
+      steps:
+        - to:
+            uri: "..."
+----
+====
+
+The default Idempotency strategy uses Atom published and updated timestamps to identify already
+read entries, by filtering all entries older that the _last read_ entry.
+
+The idempotency strategy can be changed by setting the `idempotentStrategy` option. The components support two
+strategies _out-of-the-box_, but custom strategies can be used, by referencing a subclass
+of `org.apache.camel.component.atom.AtomIdempotentStrategy`, with Apache Camel's # notation.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("file://inbox?idempotentStrategy=#myIdempotentStrategy").to("...");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="file://inbox?idempotentStrategy=#myIdempotentStrategy"/>
+  <to uri="..."/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: file://inbox
+      parameters:
+        idempotentStrategy: "#myIdempotentStrategy"
+      steps:
+        - to:
+            uri: "..."
+----
+====
+
+==== Repository idempotent strategy
+As an alternative to the default idempotent strategy, a repository based strategy can be use:
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("file://inbox?idempotentStrategy=repository").to("...");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="file://inbox?idempotentStrategy=repository"/>
+  <to uri="..."/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: file://inbox
+      parameters:
+        idempotentStrategy: repository
+      steps:
+        - to:
+            uri: "..."
+----
+====
+
+This strategy checks for idempotency by storing the Atom Entry GUID in an `IdempotentRepository`. The strategy defaults
+a MemoryIdempotentRepository, but the repository can be changes to any subclass of `IdempotentRepository`, using the
+`idempotentRepository` option.
+
+
+== Examples
+
+=== Consumer Example
+
+In this sample, we poll James Strachan's blog.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("atom://http://macstrac.blogspot.com/feeds/posts/default").to("seda:feeds");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="atom://http://macstrac.blogspot.com/feeds/posts/default"/>
+  <to uri="seda:feeds"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: atom://http://macstrac.blogspot.com/feeds/posts/default
+      steps:
+        - to:
+            uri: seda:feeds
+----
+====
+
+In this sample, we want to filter only good blogs we like to a SEDA
+queue.
+The sample also shows how to set up Camel standalone, not running
+in any Container or using Spring.
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/attachments.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/attachments.adoc
new file mode 100644
index 000000000000..35938dec1025
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/attachments.adoc
@@ -0,0 +1,34 @@
+= Attachments Component
+:doctitle: Attachments
+:shortname: attachments
+:artifactid: camel-attachments
+:description: Support for attachments on Camel messages
+:since: 3.0
+:supportlevel: Stable
+:tabs-sync-option:
+
+*Since Camel {since}*
+
+The Attachments component provides the `javax.attachments` API support for Apache Camel.
+A few Camel component uses attachments such as mail and web-service components.
+The Attachments component is included automatically when using these components.
+
+The Attachments support is on Camel `Message` level, for example to get
+the `javax.activation.DataHandler` instance of the attachment, you can do as shown below:
+
+._Java-only: retrieving an attachment via Exchange API_
+[source,java]
+----
+AttachmentMessage attMsg = exchange.getIn(AttachmentMessage.class);
+Attachment attachment = attMsg.getAttachmentObject("myAttachment");
+DataHandler dh = attachment.getDataHandler();
+----
+
+And if you want to add an attachment, to a Camel `Message` you can do as shown:
+
+._Java-only: adding an attachment via Exchange API_
+[source,java]
+----
+AttachmentMessage attMsg = exchange.getIn(AttachmentMessage.class);
+attMsg.addAttachment("message1.xml", new DataHandler(new CamelFileDataSource(new File("myMessage1.xml"))));
+----
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/avro-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/avro-component.adoc
new file mode 100644
index 000000000000..bda0ced414b9
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/avro-component.adoc
@@ -0,0 +1,355 @@
+= Avro RPC Component
+:doctitle: Avro RPC
+:shortname: avro
+:artifactid: camel-avro-rpc
+:description: Produce or consume Apache Avro RPC services.
+:since: 2.10
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Both producer and consumer are supported
+
+*Since Camel {since}*
+
+*{component-header}*
+
+This component provides support for Apache Avro's rpc, by
+providing producers and consumers endpoint for using avro over netty or
+http. Before Camel 3.2 this functionality was a part of camel-avro component.
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+[source,xml]
+----
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-avro-rpc</artifactId>
+    <version>x.x.x</version>
+    <!-- use the same version as your Camel core version -->
+</dependency>
+----
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+== Apache Avro Overview
+
+Avro allows you to define message types and a protocol using a json like
+format and then generate java code for the specified types and messages.
+An example of how a schema looks like is below.
+
+[source,json]
+----
+{"namespace": "org.apache.camel.avro.generated",
+ "protocol": "KeyValueProtocol",
+
+ "types": [
+     {"name": "Key", "type": "record",
+      "fields": [
+          {"name": "key",   "type": "string"}
+      ]
+     },
+     {"name": "Value", "type": "record",
+      "fields": [
+          {"name": "value",   "type": "string"}
+      ]
+     }
+ ],
+
+ "messages": {
+     "put": {
+         "request": [{"name": "key", "type": "Key"}, {"name": "value", "type": "Value"} ],
+         "response": "null"
+     },
+     "get": {
+         "request": [{"name": "key", "type": "Key"}],
+         "response": "Value"
+     }
+ }
+}
+----
+
+You can easily generate classes from a schema, using maven, ant etc.
+More details can be found at the
+http://avro.apache.org/docs/current/[Apache Avro documentation].
+
+However, it doesn't enforce a schema-first approach, and you can create
+schema for your existing classes.
+You can use existing protocol interfaces to make RCP calls.
+You should use interface for the protocol itself and POJO beans or primitive/String classes for parameter
+and result types. Here is an example of the class that corresponds to
+the schema above:
+
+._Java-only: protocol interface and POJO class definition for Avro RPC_
+[source,java]
+----
+package org.apache.camel.avro.reflection;
+
+public interface KeyValueProtocol {
+    void put(String key, Value value);
+    Value get(String key);
+}
+
+class Value {
+    private String value;
+    public String getValue() { return value; }
+    public void setValue(String value) { this.value = value; }
+}
+----
+
+_Note: Existing classes can be used only for RPC (see below), not in
+data format._
+
+== Usage
+
+=== Using Avro RPC in Camel
+
+As mentioned above, Avro also provides RPC support over multiple
+transports such as http and netty. Camel provides consumers and
+producers for these two transports.
+
+----
+avro:[transport]:[host]:[port][?options]
+----
+
+The supported transport values are currently http or netty.
+
+[NOTE]
+====
+You can specify the message name right in the URI:
+
+----
+avro:[transport]:[host]:[port][/messageName][?options]
+----
+====
+
+For consumers, this allows you to have multiple routes attached to the
+same socket. Dispatching to the correct route will be done by the avro
+component automatically. Route with no messageName specified (if any)
+will be used as default.
+
+When using camel producers for avro ipc, the "in" message body needs to
+contain the parameters of the operation specified in the avro protocol.
+The response will be added in the body of the "out" message.
+
+In a similar manner when using camel avro consumers for avro ipc, the
+request parameters will be placed inside the "in" message body of the
+created exchange. Once the exchange is processed, the body of the
+"out" message will be sent as a response.
+
+*Note:* By default, consumer parameters are wrapped into an array. If you've
+got only one parameter, *since 2.12* you can use `singleParameter` URI
+option to receive it directly in the "in" message body without array
+wrapping.
+
+== Examples
+
+An example of using camel avro producers via http:
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:start")
+    .to("avro:http:localhost:{{avroport}}?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol")
+    .to("log:avro");
+----
+
+XML::
++
+[source,xml]
+----
+        <route>
+            <from uri="direct:start"/>
+            <to uri="avro:http:localhost:{{avroport}}?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol"/>
+            <to uri="log:avro"/>
+        </route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:start
+      steps:
+        - to:
+            uri: avro:http:localhost:{{avroport}}
+            parameters:
+              protocolClassName: org.apache.camel.avro.generated.KeyValueProtocol
+        - to:
+            uri: log:avro
+----
+====
+
+In the example above you need to fill `CamelAvroMessageName` header.
+
+You can use the following syntax to call constant messages:
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:start")
+    .to("avro:http:localhost:{{avroport}}/put?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol")
+    .to("log:avro");
+----
+
+XML::
++
+[source,xml]
+----
+        <route>
+            <from uri="direct:start"/>
+            <to uri="avro:http:localhost:{{avroport}}/put?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol"/>
+            <to uri="log:avro"/>
+        </route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:start
+      steps:
+        - to:
+            uri: avro:http:localhost:{{avroport}}/put
+            parameters:
+              protocolClassName: org.apache.camel.avro.generated.KeyValueProtocol
+        - to:
+            uri: log:avro
+----
+====
+
+An example of consuming messages using camel avro consumers via netty:
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("avro:netty:localhost:{{avroport}}?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol")
+    .choice()
+        .when().el("${in.headers.CamelAvroMessageName == 'put'}")
+            .process("putProcessor")
+        .when().el("${in.headers.CamelAvroMessageName == 'get'}")
+            .process("getProcessor");
+----
+
+XML::
++
+[source,xml]
+----
+        <route>
+            <from uri="avro:netty:localhost:{{avroport}}?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol"/>
+            <choice>
+                <when>
+                    <el>${in.headers.CamelAvroMessageName == 'put'}</el>
+                    <process ref="putProcessor"/>
+                </when>
+                <when>
+                    <el>${in.headers.CamelAvroMessageName == 'get'}</el>
+                    <process ref="getProcessor"/>
+                </when>
+            </choice>
+        </route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: avro:netty:localhost:{{avroport}}
+      parameters:
+        protocolClassName: org.apache.camel.avro.generated.KeyValueProtocol
+      steps:
+        - choice:
+            when:
+              - el: "${in.headers.CamelAvroMessageName == 'put'}"
+                steps:
+                  - process:
+                      ref: putProcessor
+              - el: "${in.headers.CamelAvroMessageName == 'get'}"
+                steps:
+                  - process:
+                      ref: getProcessor
+----
+====
+
+You can set up two distinct routes to perform the same task:
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("avro:netty:localhost:{{avroport}}/put?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol")
+    .process("putProcessor");
+
+from("avro:netty:localhost:{{avroport}}/get?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol&singleParameter=true")
+    .process("getProcessor");
+----
+
+XML::
++
+[source,xml]
+----
+        <route>
+            <from uri="avro:netty:localhost:{{avroport}}/put?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol">
+            <process ref="putProcessor"/>
+        </route>
+        <route>
+            <from uri="avro:netty:localhost:{{avroport}}/get?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol&singleParameter=true"/>
+            <process ref="getProcessor"/>
+        </route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: avro:netty:localhost:{{avroport}}/put
+      parameters:
+        protocolClassName: org.apache.camel.avro.generated.KeyValueProtocol
+      steps:
+        - process:
+            ref: putProcessor
+- route:
+    from:
+      uri: avro:netty:localhost:{{avroport}}/get
+      parameters:
+        protocolClassName: org.apache.camel.avro.generated.KeyValueProtocol
+        singleParameter: true
+      steps:
+        - process:
+            ref: getProcessor
+----
+====
+
+In the example above, get takes only one parameter, so `singleParameter`
+is used and `getProcessor` will receive Value class directly in body,
+while `putProcessor` will receive an array of size 2 with `String` key and
+`Value` value filled as array contents.
+
+
+=== Avro via HTTP SPI
+
+The Avro RPC component offers the `org.apache.camel.component.avro.spi.AvroRpcHttpServerFactory` service provider interface (SPI) so that various platforms can provide their own implementation based on their native HTTP server.
+
+The default implementation available in `org.apache.camel:camel-avro-jetty` is based on `org.apache.avro:avro-ipc-jetty`.
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/avro-dataformat.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/avro-dataformat.adoc
new file mode 100644
index 000000000000..d03f77751fdc
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/avro-dataformat.adoc
@@ -0,0 +1,122 @@
+= Avro DataFormat
+:doctitle: Avro
+:shortname: avro
+:artifactid: camel-avro
+:description: Serialize and deserialize messages using Apache Avro binary data format
+:since: 2.14
+:supportlevel: Stable
+:tabs-sync-option:
+
+*Since Camel {since}*
+
+This component provides a dataformat for avro, which allows
+serialization and deserialization of messages using Apache Avro's binary
+dataformat. Since Camel 3.2 rpc functionality was moved into separate `camel-avro-rpc` component.
+
+TIP: There is also `camel-jackson-avro` which is a more powerful Camel dataformat for using Avro.
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+[source,xml]
+----
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-avro</artifactId>
+    <version>x.x.x</version>
+    <!-- use the same version as your Camel core version -->
+</dependency>
+----
+
+
+You can easily generate classes from a schema, using maven, ant etc.
+More details can be found at the
+http://avro.apache.org/docs/current/[Apache Avro documentation].
+
+
+== Avro Dataformat Options
+
+// dataformat options: START
+include::partial$dataformat-options.adoc[]
+// dataformat options: END
+
+== Examples
+
+=== Avro Data Format usage
+
+Using the avro data format is as easy as specifying that the class that
+you want to marshal or unmarshal in your route.
+
+._Java-only: programmatic AvroDataFormat with schema_
+[source,java]
+----
+AvroDataFormat format = new AvroDataFormat(Value.SCHEMA$);
+
+from("direct:in").marshal(format).to("direct:marshal");
+from("direct:back").unmarshal(format).to("direct:unmarshal");
+----
+
+Where Value is an Avro Maven Plugin Generated class.
+
+The same route can be expressed in XML or YAML:
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:in")
+    .marshal().avro("org.apache.camel.dataformat.avro.Message")
+    .to("log:out");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+    <from uri="direct:in"/>
+    <marshal>
+        <avro instanceClass="org.apache.camel.dataformat.avro.Message" library="ApacheAvro"/>
+    </marshal>
+    <to uri="log:out"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:in
+      steps:
+        - marshal:
+            avro:
+              instanceClass: org.apache.camel.dataformat.avro.Message
+              library: ApacheAvro
+        - to:
+            uri: log:out
+----
+====
+
+An alternative can be to specify the dataformat inside the context and
+reference it from your route.
+
+._XML-only: Spring XML data format configuration_
+[source,xml]
+----
+<camelContext id="camel" xmlns="http://camel.apache.org/schema/spring">
+     <dataFormats>
+        <avro id="avro" instanceClass="org.apache.camel.dataformat.avro.Message" library="ApacheAvro"/>
+    </dataFormats>
+    <route>
+        <from uri="direct:in"/>
+        <marshal><custom ref="avro"/></marshal>
+        <to uri="log:out"/>
+    </route>
+</camelContext>
+----
+
+In the same manner, you can unmarshal using the avro data format.
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/avroJackson2-dataformat.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/avroJackson2-dataformat.adoc
new file mode 100644
index 000000000000..b399745171b5
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/avroJackson2-dataformat.adoc
@@ -0,0 +1,100 @@
+= Avro Jackson 2 DataFormat
+:doctitle: Avro Jackson 2
+:shortname: avroJackson2
+:artifactid: camel-jackson-avro
+:description: Marshal POJOs to Avro and back using Jackson.
+:since: 3.10
+:supportlevel: Stable
+:tabs-sync-option:
+
+*Since Camel {since}*
+
+Jackson Avro is a Data Format which uses the
+https://github.com/FasterXML/jackson/[Jackson library] with the https://github.com/FasterXML/jackson-dataformats-binary[Avro extension]
+to unmarshal an Avro payload into Java objects or to marshal Java objects
+into an Avro payload.
+
+[TIP]
+====
+If you are familiar with Jackson, this Avro data format behaves in the
+same way as its JSON counterpart, and thus can be used with classes
+annotated for JSON serialization/deserialization.
+====
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("kafka:topic")
+    .unmarshal().avro(JsonNode.class)
+    .to("log:info");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="kafka:topic"/>
+  <unmarshal><avro library="Jackson"/></unmarshal>
+  <to uri="log:info"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: kafka:topic
+      steps:
+        - unmarshal:
+            avro:
+              library: Jackson
+        - to:
+            uri: log:info
+----
+====
+
+== Avro Jackson Options
+
+// dataformat options: START
+include::partial$dataformat-options.adoc[]
+// dataformat options: END
+
+== Usage
+
+=== Configuring the `SchemaResolver`
+
+Since Avro serialization is schema-based, this data format requires that you provide a SchemaResolver object
+that is able to look up the schema for each exchange that is going to be marshalled/unmarshalled.
+
+You can add a single SchemaResolver to the registry, and it will be looked up automatically.
+Or you can explicitly specify the reference to a custom SchemaResolver.
+
+=== Using custom AvroMapper
+
+You can configure `JacksonAvroDataFormat` to use a custom `AvroMapper` in case you need more control of the mapping configuration.
+
+If you set up a single `AvroMapper` in the registry, then Camel will automatic lookup and use this `AvroMapper`.
+
+== Dependencies
+
+To use Avro Jackson in your Camel routes, you need to add the dependency
+on *camel-jackson-avro*, which implements this data format.
+
+If you use Maven, you could add the following to your pom.xml,
+substituting the version number for the latest & greatest release.
+
+[source,xml]
+----
+<dependency>
+  <groupId>org.apache.camel</groupId>
+  <artifactId>camel-jackson-avro</artifactId>
+  <version>x.x.x</version>
+  <!-- use the same version as your Camel core version -->
+</dependency>
+----
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/avroJackson3-dataformat.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/avroJackson3-dataformat.adoc
new file mode 100644
index 000000000000..86d1ed6302af
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/avroJackson3-dataformat.adoc
@@ -0,0 +1,100 @@
+= Avro Jackson 3 DataFormat
+:doctitle: Avro Jackson 3
+:shortname: avroJackson3
+:artifactid: camel-jackson3-avro
+:description: Marshal POJOs to Avro and back using Jackson.
+:since: 4.19
+:supportlevel: Stable
+:tabs-sync-option:
+
+*Since Camel {since}*
+
+Jackson Avro is a Data Format which uses the
+https://github.com/FasterXML/jackson/[Jackson library] with the https://github.com/FasterXML/jackson-dataformats-binary[Avro extension]
+to unmarshal an Avro payload into Java objects or to marshal Java objects
+into an Avro payload.
+
+[TIP]
+====
+If you are familiar with Jackson, this Avro data format behaves in the
+same way as its JSON counterpart, and thus can be used with classes
+annotated for JSON serialization/deserialization.
+====
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("kafka:topic")
+    .unmarshal().avro(JsonNode.class)
+    .to("log:info");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="kafka:topic"/>
+  <unmarshal><avro library="Jackson"/></unmarshal>
+  <to uri="log:info"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: kafka:topic
+      steps:
+        - unmarshal:
+            avro:
+              library: Jackson
+        - to:
+            uri: log:info
+----
+====
+
+== Avro Jackson Options
+
+// dataformat options: START
+include::partial$dataformat-options.adoc[]
+// dataformat options: END
+
+== Usage
+
+=== Configuring the `SchemaResolver`
+
+Since Avro serialization is schema-based, this data format requires that you provide a SchemaResolver object
+that is able to look up the schema for each exchange that is going to be marshalled/unmarshalled.
+
+You can add a single SchemaResolver to the registry, and it will be looked up automatically.
+Or you can explicitly specify the reference to a custom SchemaResolver.
+
+=== Using custom AvroMapper
+
+You can configure `JacksonAvroDataFormat` to use a custom `AvroMapper` in case you need more control of the mapping configuration.
+
+If you set up a single `AvroMapper` in the registry, then Camel will automatic lookup and use this `AvroMapper`.
+
+== Dependencies
+
+To use Avro Jackson in your Camel routes, you need to add the dependency
+on *camel-jackson3-avro*, which implements this data format.
+
+If you use Maven, you could add the following to your pom.xml,
+substituting the version number for the latest & greatest release.
+
+[source,xml]
+----
+<dependency>
+  <groupId>org.apache.camel</groupId>
+  <artifactId>camel-jackson3-avro</artifactId>
+  <version>x.x.x</version>
+  <!-- use the same version as your Camel core version -->
+</dependency>
+----
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-bedrock-agent-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-bedrock-agent-component.adoc
new file mode 100644
index 000000000000..b08df9fa288a
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-bedrock-agent-component.adoc
@@ -0,0 +1,89 @@
+= AWS Bedrock Agent Component
+:doctitle: AWS Bedrock Agent
+:shortname: aws-bedrock-agent
+:artifactid: camel-aws-bedrock
+:description: Operate on AWS Bedrock through its Agent.
+:since: 4.5
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Both producer and consumer are supported
+//Manually maintained attributes
+:group: AWS
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The AWS2 Bedrock component supports invoking a supported LLM model from
+https://aws.amazon.com/bedrock/[AWS Bedrock] service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Bedrock. More information is available at
+https://aws.amazon.com/bedrock/[Amazon Bedrock].
+
+
+== URI Format
+
+-------------------------
+aws-bedrock-agent-runtime://label[?options]
+-------------------------
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+
+Required Bedrock component options
+
+You have to provide the bedrockRuntimeClient in the
+Registry or your accessKey and secretKey to access
+the https://aws.amazon.com/bedrock/[Amazon Bedrock] service.
+
+== Usage
+
+=== Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
+
+The order of evaluation for Default Credentials Provider is the following:
+
+ - Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+ - Environment variables - `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
+ - Web Identity Token from AWS STS.
+ - The shared credentials and config files.
+ - Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is set.
+ - Amazon EC2 Instance profile credentials. 
+
+You have also the possibility of using Profile Credentials Provider, by specifying the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the same time.
+
+For more information about this you can look at https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html[AWS credentials documentation]
+
+== Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+*pom.xml*
+
+[source,xml]
+---------------------------------------
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-aws-bedrock</artifactId>
+    <version>${camel-version}</version>
+</dependency>
+---------------------------------------
+
+where `$\{camel-version}` must be replaced by the actual version of Camel.
+
+
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-bedrock-agent-runtime-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-bedrock-agent-runtime-component.adoc
new file mode 100644
index 000000000000..32c2e143c7b8
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-bedrock-agent-runtime-component.adoc
@@ -0,0 +1,157 @@
+= AWS Bedrock Agent Runtime Component
+:doctitle: AWS Bedrock Agent Runtime
+:shortname: aws-bedrock-agent-runtime
+:artifactid: camel-aws-bedrock
+:description: Invoke Model of AWS Bedrock Agent Runtime service.
+:since: 4.5
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Only producer is supported
+//Manually maintained attributes
+:group: AWS
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The AWS2 Bedrock component supports invoking a supported LLM model from
+https://aws.amazon.com/bedrock/[AWS Bedrock] service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Bedrock. More information is available at
+https://aws.amazon.com/bedrock/[Amazon Bedrock].
+
+
+== URI Format
+
+-------------------------
+aws-bedrock-agent-runtime://label[?options]
+-------------------------
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+
+Required Bedrock component options
+
+You have to provide the bedrockRuntimeClient in the
+Registry or your accessKey and secretKey to access
+the https://aws.amazon.com/bedrock/[Amazon Bedrock] service.
+
+== Usage
+
+=== Supported operations
+
+The component supports the following operations on the `operation` URI option:
+
+* `retrieveAndGenerate` — Query a Bedrock Knowledge Base and generate a grounded response from the selected model.
+* `retrieve` — Run a semantic search against a Bedrock Knowledge Base and return the matched chunks without LLM generation.
+* `invokeFlow` — Invoke a Bedrock Flow by id/alias and stream the resulting events back as Camel message headers.
+
+=== Retrieving from a Bedrock Knowledge Base
+
+The `retrieve` operation performs a semantic search against a Bedrock Knowledge Base and returns the matching chunks
+without invoking an LLM. Use this when you want to plug retrieval into your own generation step, inspect retrieval
+quality, or build pagination on top of the knowledge base.
+
+Mandatory options:
+
+* `knowledgeBaseId` — the id of the Bedrock Knowledge Base to query.
+
+The body of the in-message must be a `String` containing the search query. When `pojoRequest=true`, the body must be a
+`RetrieveRequest` (any retrieval-config knobs in that POJO are honored verbatim).
+
+The retrieval configuration can be tuned per exchange via the following headers:
+
+* `CamelAwsBedrockAgentRuntimeNumberOfResults` (Integer) — maximum number of chunks to return.
+* `CamelAwsBedrockAgentRuntimeSearchType` (String) — overrides the search type (`HYBRID` or `SEMANTIC`).
+* `CamelAwsBedrockAgentRuntimeNextToken` (String) — pagination token returned by a previous call.
+
+The producer surfaces the matched chunks as the out-message body (a `List<KnowledgeBaseRetrievalResult>`) and on the
+following headers:
+
+* `CamelAwsBedrockAgentRuntimeRetrievedResults` — the same `List<KnowledgeBaseRetrievalResult>` available on the body.
+* `CamelAwsBedrockAgentRuntimeNextToken` — present when the response carries a pagination token.
+* `CamelAwsBedrockAgentRuntimeRetrieveGuardrailAction` — present when the knowledge base applies a guardrail action.
+
+=== Invoking a Bedrock Flow
+
+The `invokeFlow` operation streams flow events using the AWS SDK async client; the producer transparently allocates a
+`BedrockAgentRuntimeAsyncClient` when the endpoint is configured with `operation=invokeFlow`.
+
+Mandatory options:
+
+* `flowIdentifier` — the unique id of the flow to invoke (overridable via the
+  `CamelAwsBedrockAgentRuntimeFlowIdentifier` header).
+* `flowAliasIdentifier` — the unique id of the flow alias to invoke (overridable via the
+  `CamelAwsBedrockAgentRuntimeFlowAliasIdentifier` header).
+
+Optional options:
+
+* `enableTrace` — when `true`, the producer collects the emitted `FlowTraceEvent`s into the
+  `CamelAwsBedrockAgentRuntimeFlowTraces` header (overridable via `CamelAwsBedrockAgentRuntimeFlowEnableTrace`).
+
+The body of the in-message can be:
+
+* a `String` — wrapped in a single `FlowInput` targeting node `FlowInputNode`, output `document`;
+* a `FlowInput` instance — used as the sole input to the flow;
+* a `List<FlowInput>` — passed verbatim to the request (use this form to chain multiple flow inputs).
+
+When `pojoRequest=true`, the body must be an `InvokeFlowRequest` and is sent unchanged.
+
+The producer collects emitted events into headers:
+
+* `CamelAwsBedrockAgentRuntimeFlowOutputs` — the list of `FlowOutputEvent`s emitted by the flow.
+* `CamelAwsBedrockAgentRuntimeFlowTraces` — the list of `FlowTraceEvent`s (only when tracing is enabled).
+* `CamelAwsBedrockAgentRuntimeFlowCompletionReason` — the completion reason reported by the flow (when present).
+
+The out-message body is the document of the last `FlowOutputEvent` (decoded as `String` when the document is a string,
+otherwise the raw `Document`). When the flow emits no outputs, the body is left untouched.
+
+=== Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
+
+The order of evaluation for Default Credentials Provider is the following:
+
+ - Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+ - Environment variables - `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
+ - Web Identity Token from AWS STS.
+ - The shared credentials and config files.
+ - Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is set.
+ - Amazon EC2 Instance profile credentials. 
+
+You have also the possibility of using Profile Credentials Provider, by specifying the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the same time.
+
+For more information about this you can look at https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html[AWS credentials documentation]
+
+== Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+*pom.xml*
+
+[source,xml]
+---------------------------------------
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-aws-bedrock</artifactId>
+    <version>${camel-version}</version>
+</dependency>
+---------------------------------------
+
+where `$\{camel-version}` must be replaced by the actual version of Camel.
+
+
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-bedrock-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-bedrock-component.adoc
new file mode 100644
index 000000000000..14af8e96e6c5
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-bedrock-component.adoc
@@ -0,0 +1,298 @@
+= AWS Bedrock Component
+:doctitle: AWS Bedrock
+:shortname: aws-bedrock
+:artifactid: camel-aws-bedrock
+:description: Invoke Model of AWS Bedrock service.
+:since: 4.5
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Only producer is supported
+//Manually maintained attributes
+:group: AWS
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The AWS2 Bedrock component supports invoking a supported LLM model from
+https://aws.amazon.com/bedrock/[AWS Bedrock] service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Bedrock. More information is available at
+https://aws.amazon.com/bedrock/[Amazon Bedrock].
+
+
+== URI Format
+
+----
+aws-bedrock://label[?options]
+----
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+
+Required Bedrock component options
+
+You have to provide the bedrockRuntimeClient in the
+Registry or your accessKey and secretKey to access
+the https://aws.amazon.com/bedrock/[Amazon Bedrock] service.
+
+== Usage
+
+=== Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
+
+The order of evaluation for Default Credentials Provider is the following:
+
+ - Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+ - Environment variables - `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
+ - Web Identity Token from AWS STS.
+ - The shared credentials and config files.
+ - Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is set.
+ - Amazon EC2 Instance profile credentials. 
+
+You have also the possibility of using Profile Credentials Provider, by specifying the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the same time.
+
+For more information about this you can look at https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html[AWS credentials documentation]
+
+=== Bedrock Producer operations
+
+Camel-AWS Bedrock component provides the following operation on the producer side:
+
+- invokeTextModel
+- invokeImageModel
+- invokeEmbeddingsModel
+- invokeTextModelStreaming
+- invokeImageModelStreaming
+- invokeEmbeddingsModelStreaming
+- converse
+- converseStream
+- applyGuardrail
+
+The operation must match the model type. Text-generation models are used with `invokeTextModel`, image-generation
+models (for example `amazon.titan-image-generator-v1`, `amazon.nova-canvas-v1:0`, the `stability.*` models) with
+`invokeImageModel`, and embedding models (for example `amazon.titan-embed-text-v1`, `cohere.embed-english-v3`) with
+`invokeEmbeddingsModel`. Invoking `invokeTextModel` with an image, embedding, rerank or video/speech model fails fast
+with an `IllegalArgumentException` that names the model and points to the operation to use instead.
+
+=== Streaming Support
+
+The streaming operations (`invokeTextModelStreaming`, `invokeImageModelStreaming`, `invokeEmbeddingsModelStreaming`) enable real-time streaming of model responses, providing lower latency and better user experience for interactive applications.
+
+==== Streaming Output Modes
+
+Two streaming modes are supported:
+
+*Complete Mode (default)*: Accumulates all chunks and returns the complete response as a single message. This is the simplest mode and behaves similarly to non-streaming operations, but with lower time-to-first-token.
+
+*Chunks Mode*: Emits each chunk as it arrives in a List. Useful for reactive streaming pipelines or when you need to process chunks individually.
+
+==== Streaming Configuration Options
+
+- `streamOutputMode`: Set to "complete" (default) or "chunks"
+- `includeStreamingMetadata`: Whether to include metadata headers (default: true)
+
+==== Streaming Metadata Headers
+
+When `includeStreamingMetadata` is true, the following headers are set:
+
+- `CamelAwsBedrockCompletionReason`: The reason the model stopped generating (e.g., "FINISH", "end_turn", "stop")
+- `CamelAwsBedrockTokenCount`: The number of tokens generated (if provided by the model)
+- `CamelAwsBedrockChunkCount`: The number of chunks received
+
+==== Supported Models for Streaming
+
+All text generation models support streaming:
+- Amazon Titan (all text models)
+- Anthropic Claude (all versions)
+- Meta Llama (all versions)
+- Mistral AI (all models)
+- Cohere Command models
+- Amazon Nova models
+
+=== Converse API Support
+
+The Converse API provides a unified, model-agnostic interface for conversational AI interactions with AWS Bedrock models. It offers several advantages over the legacy InvokeModel API:
+
+- *Unified Interface*: Single API across all supported models (Claude, Llama, Mistral, etc.)
+- *Multi-turn Conversations*: Native support for conversation history with user/assistant roles
+- *Tool Use & Function Calling*: Built-in support for tools and function calling
+- *System Prompts*: First-class support for system-level instructions
+- *Structured Responses*: Consistent response format across all models
+- *Streaming Support*: Real-time streaming with the `converseStream` operation
+
+==== Converse Operations
+
+Two operations are provided:
+
+*converse*: Standard request-response conversation
+[source]
+----
+aws-bedrock://label?operation=converse&modelId=anthropic.claude-3-sonnet-20240229-v1:0
+----
+
+*converseStream*: Streaming conversation with real-time chunk delivery
+[source]
+----
+aws-bedrock://label?operation=converseStream&modelId=anthropic.claude-3-sonnet-20240229-v1:0
+----
+
+==== Converse Configuration Options
+
+Converse API uses message headers for configuration:
+
+- `CamelAwsBedrockConverseMessages` (required): List of Message objects representing the conversation
+- `CamelAwsBedrockConverseSystem`: List of SystemContentBlock for system-level instructions
+- `CamelAwsBedrockConverseInferenceConfig`: InferenceConfiguration for temperature, maxTokens, etc.
+- `CamelAwsBedrockConverseToolConfig`: ToolConfiguration for function calling support
+- `CamelAwsBedrockConverseAdditionalFields`: Document for model-specific additional fields
+
+For streaming operations, you can also use:
+- `CamelAwsBedrockStreamOutputMode`: Set to "complete" (default) or "chunks"
+
+==== Converse Response Headers
+
+When a conversation completes, the following headers are set:
+
+- `CamelAwsBedrockConverseStopReason`: Why the model stopped (e.g., "end_turn", "max_tokens")
+- `CamelAwsBedrockConverseUsage`: TokenUsage object with input/output token counts
+- `CamelAwsBedrockConverseOutputMessage`: The complete Message object from the model
+- `CamelAwsBedrockChunkCount`: (streaming only) Number of chunks received
+
+==== Supported Models for Converse API
+
+The Converse API supports all modern foundation models on Bedrock:
+
+- Anthropic Claude 3 family (Haiku, Sonnet, Opus)
+- Anthropic Claude 3.5 family (Sonnet v2, Haiku)
+- Amazon Nova family (Micro, Lite, Pro)
+- Meta Llama 3.x models
+- Mistral AI models
+- Cohere Command R models
+
+NOTE: Legacy models (Claude 2.x, Claude Instant) are not supported by the Converse API. Use the `invokeTextModel` operation for those models.
+
+=== Guardrails Support
+
+AWS Bedrock Guardrails enable you to implement safeguards for your generative AI applications based on your use cases and responsible AI policies. Guardrails can filter harmful content, block sensitive topics, remove personally identifiable information (PII), and enhance content safety and privacy in generative AI applications.
+
+The Camel AWS Bedrock component provides comprehensive support for guardrails through:
+
+- *Converse API Integration*: Apply guardrails to conversational interactions
+- *Streaming Support*: Use guardrails with real-time streaming responses
+- *Standalone Validation*: Check content against guardrails without invoking a model
+- *Flexible Configuration*: Configure guardrails at endpoint level or per-message
+
+==== Guardrails Configuration Options
+
+*Endpoint-level Configuration* (applies to all requests):
+
+- `guardrailIdentifier`: The ID or ARN of the guardrail to apply
+- `guardrailVersion`: The version of the guardrail (default: "DRAFT")
+- `guardrailTrace`: Whether to return trace information (default: false)
+
+*Message-level Configuration* (per-message override via headers):
+
+- `CamelAwsBedrockGuardrailConfig`: GuardrailConfiguration object for converse operations
+- `CamelAwsBedrockGuardrailIdentifier`: Guardrail identifier String for the applyGuardrail operation (overrides the endpoint `guardrailIdentifier`)
+- `CamelAwsBedrockGuardrailContent`: Content blocks for applyGuardrail operation
+- `CamelAwsBedrockGuardrailSource`: Source type - "INPUT" or "OUTPUT" for applyGuardrail
+
+==== Guardrails Operations
+
+*converse with Guardrails*: Apply guardrails to conversational model invocations
+
+[source]
+----
+aws-bedrock://label?operation=converse&modelId=anthropic.claude-3-sonnet-20240229-v1:0
+    &guardrailIdentifier=abc123xyz&guardrailVersion=DRAFT&guardrailTrace=true
+----
+
+*converseStream with Guardrails*: Apply guardrails to streaming conversations
+
+[source]
+----
+aws-bedrock://label?operation=converseStream&modelId=anthropic.claude-3-sonnet-20240229-v1:0
+    &guardrailIdentifier=abc123xyz&guardrailVersion=DRAFT
+----
+
+*applyGuardrail*: Standalone operation to validate content against a guardrail without invoking a model
+
+[source]
+----
+aws-bedrock://label?operation=applyGuardrail&guardrailIdentifier=abc123xyz
+    &guardrailVersion=DRAFT
+----
+
+==== Guardrails Response Headers
+
+When using guardrails, the following headers may be set in the response:
+
+- `CamelAwsBedrockGuardrailTrace`: Trace information from guardrail evaluation (when trace is enabled)
+- `CamelAwsBedrockGuardrailOutput`: Output content blocks from applyGuardrail
+- `CamelAwsBedrockGuardrailAssessments`: Detailed assessments from applyGuardrail
+- `CamelAwsBedrockGuardrailUsage`: Token usage for guardrail evaluation
+
+==== Creating a Guardrail in AWS
+
+Before using guardrails, you need to create and configure one in the AWS Bedrock console:
+
+1. Navigate to AWS Bedrock Console → Guardrails
+2. Click "Create guardrail"
+3. Configure filters:
+   - *Content filters*: Block harmful content (hate, violence, sexual, etc.)
+   - *Denied topics*: Block specific topics you define
+   - *Word filters*: Block or mask custom words/phrases
+   - *PII filters*: Detect and redact personally identifiable information
+4. Save and note your Guardrail ID (e.g., `abc123xyz`)
+
+==== Supported Models for Guardrails
+
+Guardrails work with all models that support the Converse API:
+
+- Anthropic Claude 3 family (Haiku, Sonnet, Opus)
+- Anthropic Claude 3.5 family (Sonnet v2, Haiku)
+- Amazon Nova family (Micro, Lite, Pro)
+- Meta Llama 3.x models
+- Mistral AI models
+- Cohere Command R models
+
+== Sub-Pages
+
+For more details on specific features, see:
+
+* xref:others:aws-bedrock-models.adoc[Supported Models] - Complete list of supported AWS Bedrock models with JSON request schemas
+* xref:others:aws-bedrock-examples.adoc[Examples] - Producer examples for text, image, embeddings, streaming, conversation, and guardrails
+
+== Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+*pom.xml*
+
+[source,xml]
+----
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-aws-bedrock</artifactId>
+    <version>${camel-version}</version>
+</dependency>
+----
+
+where `$\{camel-version}` must be replaced by the actual version of Camel.
+
+
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-bedrock-examples.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-bedrock-examples.adoc
new file mode 100644
index 000000000000..88e32733b0c9
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-bedrock-examples.adoc
@@ -0,0 +1,1148 @@
+= AWS Bedrock - Examples
+:tabs-sync-option:
+
+xref:ROOT:aws-bedrock-component.adoc[Back to AWS Bedrock Component]
+
+== Producer Examples
+
+- invokeTextModel: this operation will invoke a model from Bedrock. This is an example for both Titan Express and Titan Lite.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:invoke")
+    .to("aws-bedrock://test?bedrockRuntimeClient=#amazonBedrockRuntimeClient&operation=invokeTextModel&modelId=amazon.titan-text-express-v1");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:invoke"/>
+  <to uri="aws-bedrock://test?bedrockRuntimeClient=#amazonBedrockRuntimeClient&amp;operation=invokeTextModel&amp;modelId=amazon.titan-text-express-v1"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:invoke
+      steps:
+        - to:
+            uri: aws-bedrock://test
+            parameters:
+              bedrockRuntimeClient: "#amazonBedrockRuntimeClient"
+              operation: invokeTextModel
+              modelId: amazon.titan-text-express-v1
+----
+====
+
+and you can then send to the direct endpoint something like
+
+._Java-only: uses `ProducerTemplate` test API with complex JSON construction_
+[source,java]
+----
+        final Exchange result = template.send("direct:invoke", exchange -> {
+            ObjectMapper mapper = new ObjectMapper();
+            ObjectNode rootNode = mapper.createObjectNode();
+            rootNode.put("inputText",
+                    "User: Generate synthetic data for daily product sales in various categories - include row number, product name, category, date of sale and price. Produce output in JSON format. Count records and ensure there are no more than 5.");
+
+            ArrayNode stopSequences = mapper.createArrayNode();
+            stopSequences.add("User:");
+            ObjectNode childNode = mapper.createObjectNode();
+            childNode.put("maxTokenCount", 1024);
+            childNode.put("stopSequences", stopSequences);
+            childNode.put("temperature", 0).put("topP", 1);
+
+            rootNode.put("textGenerationConfig", childNode);
+            exchange.getMessage().setBody(mapper.writer().writeValueAsString(rootNode));
+            exchange.getMessage().setHeader("CamelAwsBedrockContentType", "application/json");
+            exchange.getMessage().setHeader("CamelAwsBedrockAcceptContentType", "application/json");
+        });
+----
+
+where template is a ProducerTemplate.
+
+- invokeImageModel: this operation will invoke a model from Bedrock. This is an example for Titan Image Generator.
+
+._Java-only: uses `unmarshal().base64()` method chain and `simple()` expression builder_
+[source,java]
+----
+from("direct:invoke")
+    .to("aws-bedrock://test?bedrockRuntimeClient=#amazonBedrockRuntimeClient&operation=invokeImageModel&modelId=amazon.titan-image-generator-v1")
+    .split(body())
+        .unmarshal().base64()
+        .setHeader("CamelFileName", simple("image-${random(128)}.png"))
+        .to("file:target/generated_images");
+----
+
+and you can then send to the direct endpoint something like
+
+._Java-only: uses `ProducerTemplate` test API with complex JSON construction_
+[source,java]
+----
+        final Exchange result = template.send("direct:send_titan_image", exchange -> {
+            ObjectMapper mapper = new ObjectMapper();
+            ObjectNode rootNode = mapper.createObjectNode();
+            ObjectNode textParameter = mapper.createObjectNode();
+            textParameter.putIfAbsent("text",
+                    new TextNode("A Sci-fi camel running in the desert"));
+            rootNode.putIfAbsent("textToImageParams", textParameter);
+            rootNode.putIfAbsent("taskType", new TextNode("TEXT_IMAGE"));
+            ObjectNode childNode = mapper.createObjectNode();
+            childNode.putIfAbsent("numberOfImages", new IntNode(3));
+            childNode.putIfAbsent("quality", new TextNode("standard"));
+            childNode.putIfAbsent("cfgScale", new IntNode(8));
+            childNode.putIfAbsent("height", new IntNode(512));
+            childNode.putIfAbsent("width", new IntNode(512));
+            childNode.putIfAbsent("seed", new IntNode(0));
+
+            rootNode.putIfAbsent("imageGenerationConfig", childNode);
+
+            exchange.getMessage().setBody(mapper.writer().writeValueAsString(rootNode));
+            exchange.getMessage().setHeader("CamelAwsBedrockContentType", "application/json");
+            exchange.getMessage().setHeader("CamelAwsBedrockAcceptContentType", "application/json");
+        });
+----
+
+where template is a ProducerTemplate.
+
+- invokeEmbeddingsModel: this operation will invoke an Embeddings model from Bedrock. This is an example for Titan Embeddings G1.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:send_titan_embeddings")
+    .to("aws-bedrock:label?useDefaultCredentialsProvider=true&region=us-east-1&operation=invokeEmbeddingsModel&modelId=amazon.titan-embed-text-v1")
+    .to("mock:result");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:send_titan_embeddings"/>
+  <to uri="aws-bedrock:label?useDefaultCredentialsProvider=true&amp;region=us-east-1&amp;operation=invokeEmbeddingsModel&amp;modelId=amazon.titan-embed-text-v1"/>
+  <to uri="mock:result"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:send_titan_embeddings
+      steps:
+        - to:
+            uri: aws-bedrock:label
+            parameters:
+              useDefaultCredentialsProvider: true
+              region: us-east-1
+              operation: invokeEmbeddingsModel
+              modelId: amazon.titan-embed-text-v1
+        - to:
+            uri: mock:result
+----
+====
+
+and you can then send to the direct endpoint something like
+
+._Java-only: uses `ProducerTemplate` test API with complex JSON construction_
+[source,java]
+----
+        final Exchange result = template.send("direct:send_titan_embeddings", exchange -> {
+            ObjectMapper mapper = new ObjectMapper();
+            ObjectNode rootNode = mapper.createObjectNode();
+            rootNode.putIfAbsent("inputText",
+                    new TextNode("A Sci-fi camel running in the desert"));
+
+            exchange.getMessage().setBody(mapper.writer().writeValueAsString(rootNode));
+            exchange.getMessage().setHeader("CamelAwsBedrockContentType", "application/json");
+            exchange.getMessage().setHeader("CamelAwsBedrockAcceptContentType", "*/*");
+        });
+----
+
+where template is a ProducerTemplate.
+
+- invokeTextModelStreaming (Complete Mode): this operation will invoke a model from Bedrock with streaming, accumulating the complete response.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:stream_complete")
+    .to("aws-bedrock://test?useDefaultCredentialsProvider=true&region=us-east-1&operation=invokeTextModelStreaming&modelId=amazon.titan-text-express-v1&streamOutputMode=complete")
+    .to("log:response");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:stream_complete"/>
+  <to uri="aws-bedrock://test?useDefaultCredentialsProvider=true&amp;region=us-east-1&amp;operation=invokeTextModelStreaming&amp;modelId=amazon.titan-text-express-v1&amp;streamOutputMode=complete"/>
+  <to uri="log:response"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:stream_complete
+      steps:
+        - to:
+            uri: aws-bedrock://test
+            parameters:
+              useDefaultCredentialsProvider: true
+              region: us-east-1
+              operation: invokeTextModelStreaming
+              modelId: amazon.titan-text-express-v1
+              streamOutputMode: complete
+        - to:
+            uri: log:response
+----
+====
+
+and you can then send to the direct endpoint something like
+
+._Java-only: uses `ProducerTemplate` test API with complex JSON construction_
+[source,java]
+----
+        final Exchange result = template.send("direct:stream_complete", exchange -> {
+            ObjectMapper mapper = new ObjectMapper();
+            ObjectNode rootNode = mapper.createObjectNode();
+            rootNode.put("inputText", "Write a short poem about Apache Camel.");
+
+            ArrayNode stopSequences = mapper.createArrayNode();
+            stopSequences.add("User:");
+            ObjectNode childNode = mapper.createObjectNode();
+            childNode.put("maxTokenCount", 512);
+            childNode.put("stopSequences", stopSequences);
+            childNode.put("temperature", 0).put("topP", 1);
+
+            rootNode.put("textGenerationConfig", childNode);
+            exchange.getMessage().setBody(mapper.writer().writeValueAsString(rootNode));
+            exchange.getMessage().setHeader("CamelAwsBedrockContentType", "application/json");
+            exchange.getMessage().setHeader("CamelAwsBedrockAcceptContentType", "application/json");
+        });
+
+        // Get the complete response
+        String response = result.getMessage().getBody(String.class);
+
+        // Get streaming metadata
+        Integer tokenCount = result.getMessage().getHeader("CamelAwsBedrockTokenCount", Integer.class);
+        String completionReason = result.getMessage().getHeader("CamelAwsBedrockCompletionReason", String.class);
+        Integer chunkCount = result.getMessage().getHeader("CamelAwsBedrockChunkCount", Integer.class);
+----
+
+- invokeTextModelStreaming (Chunks Mode): this operation will invoke a model from Bedrock with streaming, emitting individual chunks.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:stream_chunks")
+    .to("aws-bedrock://test?useDefaultCredentialsProvider=true&region=us-east-1&operation=invokeTextModelStreaming&modelId=anthropic.claude-3-5-sonnet-20241022-v2:0&streamOutputMode=chunks")
+    .split(body())
+        .to("websocket:chat-output");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:stream_chunks"/>
+  <to uri="aws-bedrock://test?useDefaultCredentialsProvider=true&amp;region=us-east-1&amp;operation=invokeTextModelStreaming&amp;modelId=anthropic.claude-3-5-sonnet-20241022-v2:0&amp;streamOutputMode=chunks"/>
+  <split>
+    <simple>${body}</simple>
+    <to uri="websocket:chat-output"/>
+  </split>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:stream_chunks
+      steps:
+        - to:
+            uri: aws-bedrock://test
+            parameters:
+              useDefaultCredentialsProvider: true
+              region: us-east-1
+              operation: invokeTextModelStreaming
+              modelId: "anthropic.claude-3-5-sonnet-20241022-v2:0"
+              streamOutputMode: chunks
+        - split:
+            expression:
+              simple: "${body}"
+            steps:
+              - to:
+                  uri: websocket:chat-output
+----
+====
+
+and you can then send to the direct endpoint something like
+
+._Java-only: uses `ProducerTemplate` test API with complex JSON construction_
+[source,java]
+----
+        final Exchange result = template.send("direct:stream_chunks", exchange -> {
+            ObjectMapper mapper = new ObjectMapper();
+            ObjectNode rootNode = mapper.createObjectNode();
+
+            ArrayNode messages = mapper.createArrayNode();
+            ObjectNode message = mapper.createObjectNode();
+            message.put("role", "user");
+
+            ArrayNode content = mapper.createArrayNode();
+            ObjectNode contentBlock = mapper.createObjectNode();
+            contentBlock.put("type", "text");
+            contentBlock.put("text", "Explain Apache Camel in one sentence.");
+            content.add(contentBlock);
+
+            message.put("content", content);
+            messages.add(message);
+
+            rootNode.put("messages", messages);
+            rootNode.put("max_tokens", 200);
+            rootNode.put("anthropic_version", "bedrock-2023-05-31");
+
+            exchange.getMessage().setBody(mapper.writer().writeValueAsString(rootNode));
+            exchange.getMessage().setHeader("CamelAwsBedrockContentType", "application/json");
+            exchange.getMessage().setHeader("CamelAwsBedrockAcceptContentType", "application/json");
+        });
+
+        // Get the list of chunks
+        List<String> chunks = result.getMessage().getBody(List.class);
+
+        // Process each chunk
+        for (String chunk : chunks) {
+            System.out.println("Chunk: " + chunk);
+        }
+----
+
+- converse: this operation uses the unified Converse API for model-agnostic conversations.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:converse")
+    .to("aws-bedrock://test?useDefaultCredentialsProvider=true&region=us-east-1&operation=converse&modelId=anthropic.claude-3-sonnet-20240229-v1:0")
+    .to("log:response");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:converse"/>
+  <to uri="aws-bedrock://test?useDefaultCredentialsProvider=true&amp;region=us-east-1&amp;operation=converse&amp;modelId=anthropic.claude-3-sonnet-20240229-v1:0"/>
+  <to uri="log:response"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:converse
+      steps:
+        - to:
+            uri: aws-bedrock://test
+            parameters:
+              useDefaultCredentialsProvider: true
+              region: us-east-1
+              operation: converse
+              modelId: "anthropic.claude-3-sonnet-20240229-v1:0"
+        - to:
+            uri: log:response
+----
+====
+
+and you can then send to the direct endpoint something like
+
+._Java-only: uses `ProducerTemplate` test API with AWS SDK objects_
+[source,java]
+----
+        final Exchange result = template.send("direct:converse", exchange -> {
+            // Create a conversation message
+            List<software.amazon.awssdk.services.bedrockruntime.model.Message> messages = new ArrayList<>();
+            messages.add(software.amazon.awssdk.services.bedrockruntime.model.Message.builder()
+                    .role(software.amazon.awssdk.services.bedrockruntime.model.ConversationRole.USER)
+                    .content(software.amazon.awssdk.services.bedrockruntime.model.ContentBlock
+                            .fromText("What is Apache Camel and what are its main features?"))
+                    .build());
+
+            exchange.getMessage().setHeader("CamelAwsBedrockConverseMessages", messages);
+
+            // Optional: Add inference configuration
+            software.amazon.awssdk.services.bedrockruntime.model.InferenceConfiguration inferenceConfig
+                    = software.amazon.awssdk.services.bedrockruntime.model.InferenceConfiguration.builder()
+                            .maxTokens(500)
+                            .temperature(0.7f)
+                            .build();
+            exchange.getMessage().setHeader("CamelAwsBedrockConverseInferenceConfig", inferenceConfig);
+
+            // Optional: Add system prompt
+            List<software.amazon.awssdk.services.bedrockruntime.model.SystemContentBlock> systemPrompt = new ArrayList<>();
+            systemPrompt.add(software.amazon.awssdk.services.bedrockruntime.model.SystemContentBlock
+                    .fromText("You are a helpful assistant that explains software concepts clearly and concisely."));
+            exchange.getMessage().setHeader("CamelAwsBedrockConverseSystem", systemPrompt);
+        });
+
+        // Get the response text
+        String response = result.getMessage().getBody(String.class);
+
+        // Get metadata from headers
+        String stopReason = result.getMessage().getHeader("CamelAwsBedrockConverseStopReason", String.class);
+        software.amazon.awssdk.services.bedrockruntime.model.TokenUsage usage
+                = result.getMessage().getHeader("CamelAwsBedrockConverseUsage",
+                        software.amazon.awssdk.services.bedrockruntime.model.TokenUsage.class);
+
+        System.out.println("Response: " + response);
+        System.out.println("Stop reason: " + stopReason);
+        System.out.println("Input tokens: " + usage.inputTokens());
+        System.out.println("Output tokens: " + usage.outputTokens());
+----
+
+- converseStream (Complete Mode): this operation uses the Converse API with streaming, accumulating the complete response.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:converse_stream")
+    .to("aws-bedrock://test?useDefaultCredentialsProvider=true&region=us-east-1&operation=converseStream&modelId=anthropic.claude-3-sonnet-20240229-v1:0")
+    .to("log:response");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:converse_stream"/>
+  <to uri="aws-bedrock://test?useDefaultCredentialsProvider=true&amp;region=us-east-1&amp;operation=converseStream&amp;modelId=anthropic.claude-3-sonnet-20240229-v1:0"/>
+  <to uri="log:response"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:converse_stream
+      steps:
+        - to:
+            uri: aws-bedrock://test
+            parameters:
+              useDefaultCredentialsProvider: true
+              region: us-east-1
+              operation: converseStream
+              modelId: "anthropic.claude-3-sonnet-20240229-v1:0"
+        - to:
+            uri: log:response
+----
+====
+
+and you can then send to the direct endpoint something like
+
+._Java-only: uses `ProducerTemplate` test API with AWS SDK objects_
+[source,java]
+----
+        final Exchange result = template.send("direct:converse_stream", exchange -> {
+            // Create a conversation message
+            List<software.amazon.awssdk.services.bedrockruntime.model.Message> messages = new ArrayList<>();
+            messages.add(software.amazon.awssdk.services.bedrockruntime.model.Message.builder()
+                    .role(software.amazon.awssdk.services.bedrockruntime.model.ConversationRole.USER)
+                    .content(software.amazon.awssdk.services.bedrockruntime.model.ContentBlock
+                            .fromText("Explain the Enterprise Integration Patterns in three sentences."))
+                    .build());
+
+            exchange.getMessage().setHeader("CamelAwsBedrockConverseMessages", messages);
+            exchange.getMessage().setHeader("CamelAwsBedrockStreamOutputMode", "complete");
+
+            // Optional: Add inference configuration
+            software.amazon.awssdk.services.bedrockruntime.model.InferenceConfiguration inferenceConfig
+                    = software.amazon.awssdk.services.bedrockruntime.model.InferenceConfiguration.builder()
+                            .maxTokens(300)
+                            .temperature(0.5f)
+                            .build();
+            exchange.getMessage().setHeader("CamelAwsBedrockConverseInferenceConfig", inferenceConfig);
+        });
+
+        // Get the complete streamed response
+        String response = result.getMessage().getBody(String.class);
+        Integer chunkCount = result.getMessage().getHeader("CamelAwsBedrockChunkCount", Integer.class);
+
+        System.out.println("Response: " + response);
+        System.out.println("Received " + chunkCount + " chunks");
+----
+
+- converseStream (Chunks Mode): this operation uses the Converse API with streaming, emitting individual chunks.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:converse_stream_chunks")
+    .to("aws-bedrock://test?useDefaultCredentialsProvider=true&region=us-east-1&operation=converseStream&modelId=anthropic.claude-3-sonnet-20240229-v1:0")
+    .split(body())
+        .to("websocket:chat-output");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:converse_stream_chunks"/>
+  <to uri="aws-bedrock://test?useDefaultCredentialsProvider=true&amp;region=us-east-1&amp;operation=converseStream&amp;modelId=anthropic.claude-3-sonnet-20240229-v1:0"/>
+  <split>
+    <simple>${body}</simple>
+    <to uri="websocket:chat-output"/>
+  </split>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:converse_stream_chunks
+      steps:
+        - to:
+            uri: aws-bedrock://test
+            parameters:
+              useDefaultCredentialsProvider: true
+              region: us-east-1
+              operation: converseStream
+              modelId: "anthropic.claude-3-sonnet-20240229-v1:0"
+        - split:
+            expression:
+              simple: "${body}"
+            steps:
+              - to:
+                  uri: websocket:chat-output
+----
+====
+
+and you can then send to the direct endpoint something like
+
+._Java-only: uses `ProducerTemplate` test API with AWS SDK objects_
+[source,java]
+----
+        final Exchange result = template.send("direct:converse_stream_chunks", exchange -> {
+            // Create a conversation message
+            List<software.amazon.awssdk.services.bedrockruntime.model.Message> messages = new ArrayList<>();
+            messages.add(software.amazon.awssdk.services.bedrockruntime.model.Message.builder()
+                    .role(software.amazon.awssdk.services.bedrockruntime.model.ConversationRole.USER)
+                    .content(software.amazon.awssdk.services.bedrockruntime.model.ContentBlock
+                            .fromText("Write a haiku about software integration."))
+                    .build());
+
+            exchange.getMessage().setHeader("CamelAwsBedrockConverseMessages", messages);
+            exchange.getMessage().setHeader("CamelAwsBedrockStreamOutputMode", "chunks");
+        });
+
+        // Get the list of chunks
+        List<String> chunks = result.getMessage().getBody(List.class);
+
+        // Process each chunk as it was received
+        for (String chunk : chunks) {
+            System.out.println("Chunk: " + chunk);
+        }
+----
+
+- Multi-turn Conversation with Converse API: demonstrates maintaining conversation history.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:conversation")
+    .to("aws-bedrock://test?useDefaultCredentialsProvider=true&region=us-east-1&operation=converse&modelId=anthropic.claude-3-sonnet-20240229-v1:0")
+    .to("log:response");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:conversation"/>
+  <to uri="aws-bedrock://test?useDefaultCredentialsProvider=true&amp;region=us-east-1&amp;operation=converse&amp;modelId=anthropic.claude-3-sonnet-20240229-v1:0"/>
+  <to uri="log:response"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:conversation
+      steps:
+        - to:
+            uri: aws-bedrock://test
+            parameters:
+              useDefaultCredentialsProvider: true
+              region: us-east-1
+              operation: converse
+              modelId: "anthropic.claude-3-sonnet-20240229-v1:0"
+        - to:
+            uri: log:response
+----
+====
+
+and you can then send to the direct endpoint something like
+
+._Java-only: uses `ProducerTemplate` test API with multi-turn conversation history_
+[source,java]
+----
+        // Maintain conversation history
+        List<software.amazon.awssdk.services.bedrockruntime.model.Message> conversationHistory = new ArrayList<>();
+
+        // First turn
+        conversationHistory.add(software.amazon.awssdk.services.bedrockruntime.model.Message.builder()
+                .role(software.amazon.awssdk.services.bedrockruntime.model.ConversationRole.USER)
+                .content(software.amazon.awssdk.services.bedrockruntime.model.ContentBlock
+                        .fromText("What is Apache Camel?"))
+                .build());
+
+        Exchange result1 = template.send("direct:conversation", exchange -> {
+            exchange.getMessage().setHeader("CamelAwsBedrockConverseMessages",
+                    new ArrayList<>(conversationHistory));
+        });
+
+        // Add assistant's response to history
+        software.amazon.awssdk.services.bedrockruntime.model.Message assistantMessage
+                = result1.getMessage().getHeader("CamelAwsBedrockConverseOutputMessage",
+                        software.amazon.awssdk.services.bedrockruntime.model.Message.class);
+        conversationHistory.add(assistantMessage);
+
+        // Second turn - follow-up question
+        conversationHistory.add(software.amazon.awssdk.services.bedrockruntime.model.Message.builder()
+                .role(software.amazon.awssdk.services.bedrockruntime.model.ConversationRole.USER)
+                .content(software.amazon.awssdk.services.bedrockruntime.model.ContentBlock
+                        .fromText("Can you give me a simple example?"))
+                .build());
+
+        Exchange result2 = template.send("direct:conversation", exchange -> {
+            exchange.getMessage().setHeader("CamelAwsBedrockConverseMessages",
+                    new ArrayList<>(conversationHistory));
+        });
+
+        String followUpResponse = result2.getMessage().getBody(String.class);
+        System.out.println("Follow-up response: " + followUpResponse);
+----
+
+== Guardrails Examples
+
+- Converse with Guardrails (Endpoint Configuration): Apply guardrails configured at the endpoint level.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:converse_with_guardrails")
+    .to("aws-bedrock://test?useDefaultCredentialsProvider=true&region=us-east-1&operation=converse&modelId=anthropic.claude-3-sonnet-20240229-v1:0&guardrailIdentifier=abc123xyz&guardrailVersion=DRAFT&guardrailTrace=true")
+    .to("log:response");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:converse_with_guardrails"/>
+  <to uri="aws-bedrock://test?useDefaultCredentialsProvider=true&amp;region=us-east-1&amp;operation=converse&amp;modelId=anthropic.claude-3-sonnet-20240229-v1:0&amp;guardrailIdentifier=abc123xyz&amp;guardrailVersion=DRAFT&amp;guardrailTrace=true"/>
+  <to uri="log:response"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:converse_with_guardrails
+      steps:
+        - to:
+            uri: aws-bedrock://test
+            parameters:
+              useDefaultCredentialsProvider: true
+              region: us-east-1
+              operation: converse
+              modelId: "anthropic.claude-3-sonnet-20240229-v1:0"
+              guardrailIdentifier: abc123xyz
+              guardrailVersion: DRAFT
+              guardrailTrace: true
+        - to:
+            uri: log:response
+----
+====
+
+and you can then send to the direct endpoint something like
+
+._Java-only: uses `ProducerTemplate` test API with AWS SDK objects_
+[source,java]
+----
+        final Exchange result = template.send("direct:converse_with_guardrails", exchange -> {
+            // Create a conversation message
+            List<software.amazon.awssdk.services.bedrockruntime.model.Message> messages = new ArrayList<>();
+            messages.add(software.amazon.awssdk.services.bedrockruntime.model.Message.builder()
+                    .role(software.amazon.awssdk.services.bedrockruntime.model.ConversationRole.USER)
+                    .content(software.amazon.awssdk.services.bedrockruntime.model.ContentBlock
+                            .fromText("Tell me about Paris"))
+                    .build());
+
+            exchange.getMessage().setHeader("CamelAwsBedrockConverseMessages", messages);
+
+            // Optional: Add inference configuration
+            software.amazon.awssdk.services.bedrockruntime.model.InferenceConfiguration inferenceConfig
+                    = software.amazon.awssdk.services.bedrockruntime.model.InferenceConfiguration.builder()
+                            .maxTokens(200)
+                            .temperature(0.7f)
+                            .build();
+            exchange.getMessage().setHeader("CamelAwsBedrockConverseInferenceConfig", inferenceConfig);
+        });
+
+        // Get the response
+        String response = result.getMessage().getBody(String.class);
+
+        // Check if guardrail trace is available
+        software.amazon.awssdk.services.bedrockruntime.model.GuardrailTrace trace
+                = result.getMessage().getHeader("CamelAwsBedrockGuardrailTrace",
+                        software.amazon.awssdk.services.bedrockruntime.model.GuardrailTrace.class);
+
+        if (trace != null) {
+            System.out.println("Guardrail evaluation: " + trace);
+        }
+----
+
+- Converse with Guardrails (Header Configuration): Apply guardrails configured per-message via headers.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:converse_dynamic_guardrails")
+    .to("aws-bedrock://test?useDefaultCredentialsProvider=true&region=us-east-1&operation=converse&modelId=anthropic.claude-3-sonnet-20240229-v1:0")
+    .to("log:response");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:converse_dynamic_guardrails"/>
+  <to uri="aws-bedrock://test?useDefaultCredentialsProvider=true&amp;region=us-east-1&amp;operation=converse&amp;modelId=anthropic.claude-3-sonnet-20240229-v1:0"/>
+  <to uri="log:response"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:converse_dynamic_guardrails
+      steps:
+        - to:
+            uri: aws-bedrock://test
+            parameters:
+              useDefaultCredentialsProvider: true
+              region: us-east-1
+              operation: converse
+              modelId: "anthropic.claude-3-sonnet-20240229-v1:0"
+        - to:
+            uri: log:response
+----
+====
+
+and you can then send to the direct endpoint something like
+
+._Java-only: uses `ProducerTemplate` test API with AWS SDK `GuardrailConfiguration` objects_
+[source,java]
+----
+        final Exchange result = template.send("direct:converse_dynamic_guardrails", exchange -> {
+            // Create a conversation message
+            List<software.amazon.awssdk.services.bedrockruntime.model.Message> messages = new ArrayList<>();
+            messages.add(software.amazon.awssdk.services.bedrockruntime.model.Message.builder()
+                    .role(software.amazon.awssdk.services.bedrockruntime.model.ConversationRole.USER)
+                    .content(software.amazon.awssdk.services.bedrockruntime.model.ContentBlock
+                            .fromText("What is the capital of France?"))
+                    .build());
+
+            exchange.getMessage().setHeader("CamelAwsBedrockConverseMessages", messages);
+
+            // Configure guardrail via header (can be dynamic per message)
+            software.amazon.awssdk.services.bedrockruntime.model.GuardrailConfiguration guardrailConfig
+                    = software.amazon.awssdk.services.bedrockruntime.model.GuardrailConfiguration.builder()
+                            .guardrailIdentifier("abc123xyz")  // Can be determined at runtime
+                            .guardrailVersion("DRAFT")
+                            .trace(software.amazon.awssdk.services.bedrockruntime.model.GuardrailTrace.ENABLED)
+                            .build();
+            exchange.getMessage().setHeader("CamelAwsBedrockGuardrailConfig", guardrailConfig);
+        });
+
+        String response = result.getMessage().getBody(String.class);
+        System.out.println("Protected response: " + response);
+----
+
+- Converse Stream with Guardrails: Apply guardrails to streaming conversations.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:stream_with_guardrails")
+    .to("aws-bedrock://test?useDefaultCredentialsProvider=true&region=us-east-1&operation=converseStream&modelId=anthropic.claude-3-sonnet-20240229-v1:0&guardrailIdentifier=abc123xyz&guardrailVersion=DRAFT")
+    .to("log:response");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:stream_with_guardrails"/>
+  <to uri="aws-bedrock://test?useDefaultCredentialsProvider=true&amp;region=us-east-1&amp;operation=converseStream&amp;modelId=anthropic.claude-3-sonnet-20240229-v1:0&amp;guardrailIdentifier=abc123xyz&amp;guardrailVersion=DRAFT"/>
+  <to uri="log:response"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:stream_with_guardrails
+      steps:
+        - to:
+            uri: aws-bedrock://test
+            parameters:
+              useDefaultCredentialsProvider: true
+              region: us-east-1
+              operation: converseStream
+              modelId: "anthropic.claude-3-sonnet-20240229-v1:0"
+              guardrailIdentifier: abc123xyz
+              guardrailVersion: DRAFT
+        - to:
+            uri: log:response
+----
+====
+
+and you can then send to the direct endpoint something like
+
+._Java-only: uses `ProducerTemplate` test API with AWS SDK objects_
+[source,java]
+----
+        final Exchange result = template.send("direct:stream_with_guardrails", exchange -> {
+            List<software.amazon.awssdk.services.bedrockruntime.model.Message> messages = new ArrayList<>();
+            messages.add(software.amazon.awssdk.services.bedrockruntime.model.Message.builder()
+                    .role(software.amazon.awssdk.services.bedrockruntime.model.ConversationRole.USER)
+                    .content(software.amazon.awssdk.services.bedrockruntime.model.ContentBlock
+                            .fromText("Tell me a story about space exploration"))
+                    .build());
+
+            exchange.getMessage().setHeader("CamelAwsBedrockConverseMessages", messages);
+            exchange.getMessage().setHeader("CamelAwsBedrockStreamOutputMode", "complete");
+        });
+
+        String streamedResponse = result.getMessage().getBody(String.class);
+        System.out.println("Guardrail-protected stream response: " + streamedResponse);
+----
+
+- Apply Guardrail: Validate content against a guardrail without invoking a model.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:validate_content")
+    .to("aws-bedrock://test?useDefaultCredentialsProvider=true&region=us-east-1&operation=applyGuardrail&guardrailIdentifier=abc123xyz&guardrailVersion=DRAFT")
+    .to("log:validation_result");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:validate_content"/>
+  <to uri="aws-bedrock://test?useDefaultCredentialsProvider=true&amp;region=us-east-1&amp;operation=applyGuardrail&amp;guardrailIdentifier=abc123xyz&amp;guardrailVersion=DRAFT"/>
+  <to uri="log:validation_result"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:validate_content
+      steps:
+        - to:
+            uri: aws-bedrock://test
+            parameters:
+              useDefaultCredentialsProvider: true
+              region: us-east-1
+              operation: applyGuardrail
+              guardrailIdentifier: abc123xyz
+              guardrailVersion: DRAFT
+        - to:
+            uri: log:validation_result
+----
+====
+
+and you can then send to the direct endpoint something like
+
+._Java-only: uses `ProducerTemplate` test API with AWS SDK `GuardrailContentBlock` objects_
+[source,java]
+----
+        final Exchange result = template.send("direct:validate_content", exchange -> {
+            // Create content blocks to check
+            List<software.amazon.awssdk.services.bedrockruntime.model.GuardrailContentBlock> content
+                    = new ArrayList<>();
+            content.add(software.amazon.awssdk.services.bedrockruntime.model.GuardrailContentBlock.builder()
+                    .text(software.amazon.awssdk.services.bedrockruntime.model.GuardrailTextBlock.builder()
+                            .text("This is the content I want to validate before sending to the model.")
+                            .build())
+                    .build());
+
+            exchange.getMessage().setHeader("CamelAwsBedrockGuardrailContent", content);
+            exchange.getMessage().setHeader("CamelAwsBedrockGuardrailSource", "INPUT");
+        });
+
+        // Get the action result (GUARDRAIL_INTERVENED or NONE)
+        String action = result.getMessage().getBody(String.class);
+
+        if ("GUARDRAIL_INTERVENED".equals(action)) {
+            System.out.println("Content was blocked by guardrail!");
+
+            // Get the assessments to see why it was blocked
+            List<?> assessments = result.getMessage().getHeader("CamelAwsBedrockGuardrailAssessments", List.class);
+            System.out.println("Reasons: " + assessments);
+
+            // Get the filtered output
+            List<?> outputs = result.getMessage().getHeader("CamelAwsBedrockGuardrailOutput", List.class);
+            System.out.println("Filtered content: " + outputs);
+        } else {
+            System.out.println("Content passed guardrail validation");
+        }
+----
+
+- Apply Guardrail with POJO Request: Use the SDK request object directly for maximum control.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:validate_pojo")
+    .to("aws-bedrock://test?useDefaultCredentialsProvider=true&region=us-east-1&operation=applyGuardrail&pojoRequest=true")
+    .to("log:validation_result");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:validate_pojo"/>
+  <to uri="aws-bedrock://test?useDefaultCredentialsProvider=true&amp;region=us-east-1&amp;operation=applyGuardrail&amp;pojoRequest=true"/>
+  <to uri="log:validation_result"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:validate_pojo
+      steps:
+        - to:
+            uri: aws-bedrock://test
+            parameters:
+              useDefaultCredentialsProvider: true
+              region: us-east-1
+              operation: applyGuardrail
+              pojoRequest: true
+        - to:
+            uri: log:validation_result
+----
+====
+
+and you can then send to the direct endpoint something like
+
+._Java-only: uses `ProducerTemplate` test API with AWS SDK `ApplyGuardrailRequest` POJO_
+[source,java]
+----
+        final Exchange result = template.send("direct:validate_pojo", exchange -> {
+            // Create content blocks
+            List<software.amazon.awssdk.services.bedrockruntime.model.GuardrailContentBlock> content
+                    = new ArrayList<>();
+            content.add(software.amazon.awssdk.services.bedrockruntime.model.GuardrailContentBlock.builder()
+                    .text(software.amazon.awssdk.services.bedrockruntime.model.GuardrailTextBlock.builder()
+                            .text("User-generated content to validate")
+                            .build())
+                    .build());
+
+            // Build the complete request object
+            software.amazon.awssdk.services.bedrockruntime.model.ApplyGuardrailRequest request
+                    = software.amazon.awssdk.services.bedrockruntime.model.ApplyGuardrailRequest.builder()
+                            .guardrailIdentifier("abc123xyz")
+                            .guardrailVersion("DRAFT")
+                            .source(software.amazon.awssdk.services.bedrockruntime.model.GuardrailContentSource.INPUT)
+                            .content(content)
+                            .build();
+
+            exchange.getMessage().setBody(request);
+        });
+
+        String action = result.getMessage().getBody(String.class);
+        System.out.println("Validation result: " + action);
+----
+
+- Content Moderation Pipeline: Combine guardrails with model invocation in a pipeline.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:moderated_conversation")
+    .to("aws-bedrock://validate?useDefaultCredentialsProvider=true&region=us-east-1&operation=applyGuardrail&guardrailIdentifier=abc123xyz")
+    .choice()
+        .when(simple("${body} == 'GUARDRAIL_INTERVENED'"))
+            .log("Input blocked by guardrail")
+            .setBody(constant("Sorry, I cannot process this request."))
+        .otherwise()
+            .to("aws-bedrock://converse?useDefaultCredentialsProvider=true&region=us-east-1&operation=converse&modelId=anthropic.claude-3-sonnet-20240229-v1:0&guardrailIdentifier=abc123xyz")
+            .log("Model response: ${body}")
+    .end()
+    .to("mock:result");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:moderated_conversation"/>
+  <to uri="aws-bedrock://validate?useDefaultCredentialsProvider=true&amp;region=us-east-1&amp;operation=applyGuardrail&amp;guardrailIdentifier=abc123xyz"/>
+  <choice>
+    <when>
+      <simple>${body} == 'GUARDRAIL_INTERVENED'</simple>
+      <log message="Input blocked by guardrail"/>
+      <setBody><constant>Sorry, I cannot process this request.</constant></setBody>
+    </when>
+    <otherwise>
+      <to uri="aws-bedrock://converse?useDefaultCredentialsProvider=true&amp;region=us-east-1&amp;operation=converse&amp;modelId=anthropic.claude-3-sonnet-20240229-v1:0&amp;guardrailIdentifier=abc123xyz"/>
+      <log message="Model response: ${body}"/>
+    </otherwise>
+  </choice>
+  <to uri="mock:result"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:moderated_conversation
+      steps:
+        - to:
+            uri: aws-bedrock://validate
+            parameters:
+              useDefaultCredentialsProvider: true
+              region: us-east-1
+              operation: applyGuardrail
+              guardrailIdentifier: abc123xyz
+        - choice:
+            when:
+              - simple: "${body} == 'GUARDRAIL_INTERVENED'"
+                steps:
+                  - log: "Input blocked by guardrail"
+                  - setBody:
+                      constant: "Sorry, I cannot process this request."
+            otherwise:
+              steps:
+                - to:
+                    uri: aws-bedrock://converse
+                    parameters:
+                      useDefaultCredentialsProvider: true
+                      region: us-east-1
+                      operation: converse
+                      modelId: "anthropic.claude-3-sonnet-20240229-v1:0"
+                      guardrailIdentifier: abc123xyz
+                - log: "Model response: ${body}"
+        - to:
+            uri: mock:result
+----
+====
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-bedrock-models.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-bedrock-models.adoc
new file mode 100644
index 000000000000..c6877ec33ea2
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-bedrock-models.adoc
@@ -0,0 +1,604 @@
+= AWS Bedrock - Supported Models
+:tabs-sync-option:
+
+xref:ROOT:aws-bedrock-component.adoc[Back to AWS Bedrock Component]
+
+== Supported AWS Bedrock Models
+
+- Titan Text Express V1 with id `amazon.titan-text-express-v1`
+Express is a large language model for text generation. It is useful for a wide range of advanced, general language tasks such as open-ended text generation and conversational chat, as well as support within Retrieval Augmented Generation (RAG).
+
+Json schema for request
+
+[source,json]
+----
+{
+  "$schema": "http://json-schema.org/draft-04/schema#",
+  "type": "object",
+  "properties": {
+    "inputText": {
+      "type": "string"
+    },
+    "textGenerationConfig": {
+      "type": "object",
+      "properties": {
+        "maxTokenCount": {
+          "type": "integer"
+        },
+        "stopSequences": {
+          "type": "array",
+          "items": [
+            {
+              "type": "string"
+            }
+          ]
+        },
+        "temperature": {
+          "type": "integer"
+        },
+        "topP": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "maxTokenCount",
+        "stopSequences",
+        "temperature",
+        "topP"
+      ]
+    }
+  },
+  "required": [
+    "inputText",
+    "textGenerationConfig"
+  ]
+}
+----
+
+- Titan Text Lite V1 with id `amazon.titan-text-lite-v1`
+Lite is a light weight efficient model, ideal for fine-tuning of English-language tasks.
+
+Json schema for request
+
+[source,json]
+----
+{
+  "$schema": "http://json-schema.org/draft-04/schema#",
+  "type": "object",
+  "properties": {
+    "inputText": {
+      "type": "string"
+    },
+    "textGenerationConfig": {
+      "type": "object",
+      "properties": {
+        "maxTokenCount": {
+          "type": "integer"
+        },
+        "stopSequences": {
+          "type": "array",
+          "items": [
+            {
+              "type": "string"
+            }
+          ]
+        },
+        "temperature": {
+          "type": "integer"
+        },
+        "topP": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "maxTokenCount",
+        "stopSequences",
+        "temperature",
+        "topP"
+      ]
+    }
+  },
+  "required": [
+    "inputText",
+    "textGenerationConfig"
+  ]
+}
+----
+
+- Titan Image Generator G1 with id `amazon.titan-image-generator-v1`
+It generates images from text, and allows users to upload and edit an existing image. Users can edit an image with a text prompt (without a mask) or parts of an image with an image mask. You can extend the boundaries of an image with outpainting, and fill in an image with inpainting.
+
+Json schema for request
+
+[source,json]
+----
+{
+  "$schema": "http://json-schema.org/draft-04/schema#",
+  "type": "object",
+  "properties": {
+    "textToImageParams": {
+      "type": "object",
+      "properties": {
+        "text": {
+          "type": "string"
+        },
+        "negativeText": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "text",
+        "negativeText"
+      ]
+    },
+    "taskType": {
+      "type": "string"
+    },
+    "imageGenerationConfig": {
+      "type": "object",
+      "properties": {
+        "cfgScale": {
+          "type": "integer"
+        },
+        "seed": {
+          "type": "integer"
+        },
+        "quality": {
+          "type": "string"
+        },
+        "width": {
+          "type": "integer"
+        },
+        "height": {
+          "type": "integer"
+        },
+        "numberOfImages": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "cfgScale",
+        "seed",
+        "quality",
+        "width",
+        "height",
+        "numberOfImages"
+      ]
+    }
+  },
+  "required": [
+    "textToImageParams",
+    "taskType",
+    "imageGenerationConfig"
+  ]
+}
+----
+
+- Titan Embeddings G1 with id `amazon.titan-embed-text-v1`
+The Amazon Titan Embeddings G1 - Text – Text v1.2 can intake up to 8k tokens and outputs a vector of 1,536 dimensions. The model also works in 25+ different language
+
+Json schema for request
+
+[source,json]
+----
+{
+  "$schema": "http://json-schema.org/draft-04/schema#",
+  "type": "object",
+  "properties": {
+    "inputText": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "inputText"
+  ]
+}
+----
+
+- Jurassic2-Ultra with id `ai21.j2-ultra-v1`
+Jurassic-2 Ultra is AI21's most powerful model for complex tasks that require advanced text generation and comprehension.
+
+Json schema for request
+
+[source,json]
+----
+{
+  "$schema": "http://json-schema.org/draft-04/schema#",
+  "type": "object",
+  "properties": {
+    "prompt": {
+      "type": "string"
+    },
+    "maxTokens": {
+      "type": "integer"
+    },
+    "temperature": {
+      "type": "integer"
+    },
+    "topP": {
+      "type": "integer"
+    },
+    "stopSequences": {
+      "type": "array",
+      "items": [
+        {
+          "type": "string"
+        }
+      ]
+    },
+    "presencePenalty": {
+      "type": "object",
+      "properties": {
+        "scale": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "scale"
+      ]
+    },
+    "frequencyPenalty": {
+      "type": "object",
+      "properties": {
+        "scale": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "scale"
+      ]
+    }
+  },
+  "required": [
+    "prompt",
+    "maxTokens",
+    "temperature",
+    "topP",
+    "stopSequences",
+    "presencePenalty",
+    "frequencyPenalty"
+  ]
+}
+----
+
+- Jurassic2-Mid with id `ai21.j2-mid-v1`
+Jurassic-2 Mid is less powerful than Ultra, yet carefully designed to strike the right balance between exceptional quality and affordability.
+
+Json schema for request
+
+[source,json]
+----
+{
+  "$schema": "http://json-schema.org/draft-04/schema#",
+  "type": "object",
+  "properties": {
+    "prompt": {
+      "type": "string"
+    },
+    "maxTokens": {
+      "type": "integer"
+    },
+    "temperature": {
+      "type": "integer"
+    },
+    "topP": {
+      "type": "integer"
+    },
+    "stopSequences": {
+      "type": "array",
+      "items": [
+        {
+          "type": "string"
+        }
+      ]
+    },
+    "presencePenalty": {
+      "type": "object",
+      "properties": {
+        "scale": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "scale"
+      ]
+    },
+    "frequencyPenalty": {
+      "type": "object",
+      "properties": {
+        "scale": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "scale"
+      ]
+    }
+  },
+  "required": [
+    "prompt",
+    "maxTokens",
+    "temperature",
+    "topP",
+    "stopSequences",
+    "presencePenalty",
+    "frequencyPenalty"
+  ]
+}
+----
+
+- Claude Instant V1.2 with id `anthropic.claude-instant-v1`
+A fast, affordable yet still very capable model, which can handle a range of tasks including casual dialogue, text analysis, summarization, and document question-answering.
+
+Json schema for request
+
+[source,json]
+----
+{
+  "$schema": "http://json-schema.org/draft-04/schema#",
+  "type": "object",
+  "properties": {
+    "prompt": {
+      "type": "string"
+    },
+    "max_tokens_to_sample": {
+      "type": "integer"
+    },
+    "stop_sequences": {
+      "type": "array",
+      "items": [
+        {
+          "type": "string"
+        }
+      ]
+    },
+    "temperature": {
+      "type": "number"
+    },
+    "top_p": {
+      "type": "integer"
+    },
+    "top_k": {
+      "type": "integer"
+    },
+    "anthropic_version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "prompt",
+    "max_tokens_to_sample",
+    "stop_sequences",
+    "temperature",
+    "top_p",
+    "top_k",
+    "anthropic_version"
+  ]
+}
+----
+
+- Claude 2 with id `anthropic.claude-v2`
+Anthropic's highly capable model across a wide range of tasks from sophisticated dialogue and creative content generation to detailed instruction following.
+
+Json schema for request
+
+[source,json]
+----
+{
+  "$schema": "http://json-schema.org/draft-04/schema#",
+  "type": "object",
+  "properties": {
+    "prompt": {
+      "type": "string"
+    },
+    "max_tokens_to_sample": {
+      "type": "integer"
+    },
+    "stop_sequences": {
+      "type": "array",
+      "items": [
+        {
+          "type": "string"
+        }
+      ]
+    },
+    "temperature": {
+      "type": "number"
+    },
+    "top_p": {
+      "type": "integer"
+    },
+    "top_k": {
+      "type": "integer"
+    },
+    "anthropic_version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "prompt",
+    "max_tokens_to_sample",
+    "stop_sequences",
+    "temperature",
+    "top_p",
+    "top_k",
+    "anthropic_version"
+  ]
+}
+----
+
+- Claude 2.1 with id `anthropic.claude-v2:1`
+An update to Claude 2 that features double the context window, plus improvements across reliability, hallucination rates, and evidence-based accuracy in long document and RAG contexts.
+
+Json schema for request
+
+[source,json]
+----
+{
+  "$schema": "http://json-schema.org/draft-04/schema#",
+  "type": "object",
+  "properties": {
+    "prompt": {
+      "type": "string"
+    },
+    "max_tokens_to_sample": {
+      "type": "integer"
+    },
+    "stop_sequences": {
+      "type": "array",
+      "items": [
+        {
+          "type": "string"
+        }
+      ]
+    },
+    "temperature": {
+      "type": "number"
+    },
+    "top_p": {
+      "type": "integer"
+    },
+    "top_k": {
+      "type": "integer"
+    },
+    "anthropic_version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "prompt",
+    "max_tokens_to_sample",
+    "stop_sequences",
+    "temperature",
+    "top_p",
+    "top_k",
+    "anthropic_version"
+  ]
+}
+----
+
+- Claude 3 Sonnet with id `anthropic.claude-3-sonnet-20240229-v1:0`
+Claude 3 Sonnet by Anthropic strikes the ideal balance between intelligence and speed—particularly for enterprise workloads.
+
+Json schema for request
+
+[source,json]
+----
+{
+  "$schema": "http://json-schema.org/draft-04/schema#",
+  "type": "object",
+  "properties": {
+    "messages": {
+      "type": "array",
+      "items": [
+        {
+          "type": "object",
+          "properties": {
+            "role": {
+              "type": "string"
+            },
+            "content": {
+              "type": "array",
+              "items": [
+                {
+                  "type": "object",
+                  "properties": {
+                    "type": {
+                      "type": "string"
+                    },
+                    "text": {
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "type",
+                    "text"
+                  ]
+                }
+              ]
+            }
+          },
+          "required": [
+            "role",
+            "content"
+          ]
+        }
+      ]
+    },
+    "max_tokens": {
+      "type": "integer"
+    },
+    "anthropic_version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "messages",
+    "max_tokens",
+    "anthropic_version"
+  ]
+}
+----
+
+- Claude 3 Haiku with id `anthropic.claude-3-haiku-20240307-v1:0`
+Claude 3 Haiku is Anthropic's fastest, most compact model for near-instant responsiveness. It answers simple queries and requests with speed.
+
+Json schema for request
+
+[source,json]
+----
+{
+  "$schema": "http://json-schema.org/draft-04/schema#",
+  "type": "object",
+  "properties": {
+    "messages": {
+      "type": "array",
+      "items": [
+        {
+          "type": "object",
+          "properties": {
+            "role": {
+              "type": "string"
+            },
+            "content": {
+              "type": "array",
+              "items": [
+                {
+                  "type": "object",
+                  "properties": {
+                    "type": {
+                      "type": "string"
+                    },
+                    "text": {
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "type",
+                    "text"
+                  ]
+                }
+              ]
+            }
+          },
+          "required": [
+            "role",
+            "content"
+          ]
+        }
+      ]
+    },
+    "max_tokens": {
+      "type": "integer"
+    },
+    "anthropic_version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "messages",
+    "max_tokens",
+    "anthropic_version"
+  ]
+}
+----
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-cloudtrail-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-cloudtrail-component.adoc
new file mode 100644
index 000000000000..93c412db64ab
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-cloudtrail-component.adoc
@@ -0,0 +1,76 @@
+= AWS CloudTrail Component
+:doctitle: AWS CloudTrail
+:shortname: aws-cloudtrail
+:artifactid: camel-aws-cloudtrail
+:description: Consume events from Amazon CloudTrail using AWS SDK version 2.x.
+:since: 3.19
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Only consumer is supported
+//Manually maintained attributes
+:group: AWS
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The AWS CloudTrail component supports receiving events from Amazon CloudTrail
+service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon CloudTrail. More information is available
+at https://aws.amazon.com/cloudtrail/[AWS CloudTrail]
+
+== URI Format
+
+-----------------------------------
+aws-cloudtrail://label[?options]
+-----------------------------------
+
+The stream needs to be created prior to it being used.
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+== Usage
+
+=== Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
+
+The order of evaluation for Default Credentials Provider is the following:
+
+- Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+- Environment variables - `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
+- Web Identity Token from AWS STS.
+- The shared credentials and config files.
+- Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is set.
+- Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by specifying the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the same time.
+
+For more information about this you can look at https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html[AWS credentials documentation]
+
+=== CloudTrail Events consumed
+
+The CloudTrail consumer will use an API method called LookupEvents.
+
+This method will only take into account management events like create/update/delete of resources and CloudTrail insight events where enabled.
+
+This means you won't consume the events registered in the CloudTrail logs stored on S3, in case of creation of a new Trail.
+
+This is important to notice, and it must be taken into account when using this component.
+
+
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-config-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-config-component.adoc
new file mode 100644
index 000000000000..6c9d40205ef7
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-config-component.adoc
@@ -0,0 +1,69 @@
+= AWS Config Service Component
+:doctitle: AWS Config Service
+:shortname: aws-config
+:artifactid: camel-aws-config
+:description: Manage AWS Config service.
+:since: 4.3
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Only producer is supported
+//Manually maintained attributes
+:group: AWS
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The AWS Config component supports create and delete config rules
+https://aws.amazon.com/config/[AWS ECS] clusters instances.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Config. More information is available at
+https://aws.amazon.com/config/[Amazon Config].
+
+== URI Format
+
+-------------------------
+aws-config://label[?options]
+-------------------------
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+Required Config component options
+
+You have to provide the ConfigClient in the
+Registry or your accessKey and secretKey to access
+the https://aws.amazon.com/config/[Amazon Config] service.
+
+== Usage
+
+=== Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
+
+The order of evaluation for Default Credentials Provider is the following:
+
+ - Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+ - Environment variables - `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
+ - Web Identity Token from AWS STS.
+ - The shared credentials and config files.
+ - Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is set.
+ - Amazon EC2 Instance profile credentials. 
+
+You have also the possibility of using Profile Credentials Provider, by specifying the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the same time.
+
+For more information about this you can look at https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html[AWS credentials documentation]
+
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-secrets-manager-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-secrets-manager-component.adoc
new file mode 100644
index 000000000000..a0e521f61bdb
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-secrets-manager-component.adoc
@@ -0,0 +1,564 @@
+= AWS Secrets Manager Component
+:doctitle: AWS Secrets Manager
+:shortname: aws-secrets-manager
+:artifactid: camel-aws-secrets-manager
+:description: Manage secrets using AWS Secrets Manager.
+:since: 3.9
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Only producer is supported
+//Manually maintained attributes
+:group: AWS
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The AWS Secrets Manager component supports https://aws.amazon.com/secrets-manager/[AWS Secrets Manager] service.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Secrets Manager. More information is available at
+https://aws.amazon.com/secrets-manager/[AWS Secrets Manager].
+
+
+== URI Format
+
+-------------------------
+aws-secrets-manager://label[?options]
+-------------------------
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+=== Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
+
+The order of evaluation for Default Credentials Provider is the following:
+
+ - Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+ - Environment variables - `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
+ - Web Identity Token from AWS STS.
+ - The shared credentials and config files.
+ - Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is set.
+ - Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by specifying the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the same time.
+
+For more information about this you can look at https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html[AWS credentials documentation]
+
+=== Using AWS Secrets Manager Property Function
+
+To use this function, you'll need to provide credentials to AWS Secrets Manager Service as environment variables:
+
+[source,bash]
+----
+export CAMEL_VAULT_AWS_ACCESS_KEY=accessKey
+export CAMEL_VAULT_AWS_SECRET_KEY=secretKey
+export CAMEL_VAULT_AWS_REGION=region
+----
+
+You can also configure the credentials in the `application.properties` file such as:
+
+[source,properties]
+----
+camel.vault.aws.accessKey = accessKey
+camel.vault.aws.secretKey = secretKey
+camel.vault.aws.region = region
+----
+
+NOTE: if you're running the application on a Kubernetes based cloud platform, you can initialize the environment variables from a Secret or Configmap to enhance security. You can also enhance security by xref:manual::using-propertyplaceholder.adoc#_resolving_property_placeholders_on_cloud[setting a Secret property placeholder] which will be initialized at application runtime only.
+
+If you want instead to use the https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html[AWS default credentials provider], you'll need to provide the following env variables:
+
+[source,bash]
+----
+export CAMEL_VAULT_AWS_USE_DEFAULT_CREDENTIALS_PROVIDER=true
+export CAMEL_VAULT_AWS_REGION=region
+----
+
+You can also configure the credentials in the `application.properties` file such as:
+
+[source,properties]
+----
+camel.vault.aws.defaultCredentialsProvider = true
+camel.vault.aws.region = region
+----
+
+It is also possible to specify a particular profile name for accessing AWS Secrets Manager
+
+[source,bash]
+----
+export CAMEL_VAULT_AWS_USE_PROFILE_CREDENTIALS_PROVIDER=true
+export CAMEL_VAULT_AWS_PROFILE_NAME=test-account
+export CAMEL_VAULT_AWS_REGION=region
+----
+
+You can also configure the credentials in the `application.properties` file such as:
+
+[source,properties]
+----
+camel.vault.aws.profileCredentialsProvider = true
+camel.vault.aws.profileName = test-account
+camel.vault.aws.region = region
+----
+
+NOTE: `camel.vault.aws` configuration only applies to the AWS Secrets Manager properties function (E.g when resolving properties).
+When using the `operation` option to create, get, list secrets etc., you should provide the usual options for connecting to AWS Services.
+
+At this point, you'll be able to reference a property in the following way:
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:start")
+    .to("{{aws:route}}");
+----
+
+XML::
++
+[source,xml]
+----
+<camelContext>
+    <route>
+        <from uri="direct:start"/>
+        <to uri="{{aws:route}}"/>
+    </route>
+</camelContext>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:start
+      steps:
+        - to:
+            uri: "{{aws:route}}"
+----
+====
+
+Where route will be the name of the secret stored in the AWS Secrets Manager Service.
+
+You could specify a default value in case the secret is not present on AWS Secret Manager:
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:start")
+    .to("{{aws:route:default}}");
+----
+
+XML::
++
+[source,xml]
+----
+<camelContext>
+    <route>
+        <from uri="direct:start"/>
+        <to uri="{{aws:route:default}}"/>
+    </route>
+</camelContext>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:start
+      steps:
+        - to:
+            uri: "{{aws:route:default}}"
+----
+====
+
+In this case, if the secret doesn't exist, the property will fall back to "default" as value.
+
+Also, you are able to get a particular field of the secret, if you have, for example, a secret named database of this form:
+
+[source,bash]
+----
+{
+  "username": "admin",
+  "password": "password123",
+  "engine": "postgres",
+  "host": "127.0.0.1",
+  "port": "3128",
+  "dbname": "db"
+}
+----
+
+You're able to do get single secret value in your route, like for example:
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:start")
+    .log("Username is {{aws:database#username}}");
+----
+
+XML::
++
+[source,xml]
+----
+<camelContext>
+    <route>
+        <from uri="direct:start"/>
+        <log message="Username is {{aws:database#username}}"/>
+    </route>
+</camelContext>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:start
+      steps:
+        - log:
+            message: "Username is {{aws:database#username}}"
+----
+====
+
+Or re-use the property as part of an endpoint.
+
+You could specify a default value in case the particular field of secret is not present on AWS Secret Manager:
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:start")
+    .log("Username is {{aws:database#username:admin}}");
+----
+
+XML::
++
+[source,xml]
+----
+<camelContext>
+    <route>
+        <from uri="direct:start"/>
+        <log message="Username is {{aws:database#username:admin}}"/>
+    </route>
+</camelContext>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:start
+      steps:
+        - log:
+            message: "Username is {{aws:database#username:admin}}"
+----
+====
+
+In this case, if the secret doesn't exist or the secret exists, but the username field is not part of the secret, the property will fall back to "admin" as value.
+
+There is also the syntax to get a particular version of the secret for both the approach, with field/default value specified or only with secret:
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:start")
+    .to("{{aws:route@bf9b4f4b-8e63-43fd-a73c-3e2d3748b451}}");
+----
+
+XML::
++
+[source,xml]
+----
+<camelContext>
+    <route>
+        <from uri="direct:start"/>
+        <to uri="{{aws:route@bf9b4f4b-8e63-43fd-a73c-3e2d3748b451}}"/>
+    </route>
+</camelContext>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:start
+      steps:
+        - to:
+            uri: "{{aws:route@bf9b4f4b-8e63-43fd-a73c-3e2d3748b451}}"
+----
+====
+
+This approach will return the RAW route secret with the version 'bf9b4f4b-8e63-43fd-a73c-3e2d3748b451'.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:start")
+    .to("{{aws:route:default@bf9b4f4b-8e63-43fd-a73c-3e2d3748b451}}");
+----
+
+XML::
++
+[source,xml]
+----
+<camelContext>
+    <route>
+        <from uri="direct:start"/>
+        <to uri="{{aws:route:default@bf9b4f4b-8e63-43fd-a73c-3e2d3748b451}}"/>
+    </route>
+</camelContext>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:start
+      steps:
+        - to:
+            uri: "{{aws:route:default@bf9b4f4b-8e63-43fd-a73c-3e2d3748b451}}"
+----
+====
+
+This approach will return the route secret value with version 'bf9b4f4b-8e63-43fd-a73c-3e2d3748b451' or default value in case the secret doesn't exist or the version doesn't exist.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:start")
+    .log("Username is {{aws:database#username:admin@bf9b4f4b-8e63-43fd-a73c-3e2d3748b451}}");
+----
+
+XML::
++
+[source,xml]
+----
+<camelContext>
+    <route>
+        <from uri="direct:start"/>
+        <log message="Username is {{aws:database#username:admin@bf9b4f4b-8e63-43fd-a73c-3e2d3748b451}}"/>
+    </route>
+</camelContext>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:start
+      steps:
+        - log:
+            message: "Username is {{aws:database#username:admin@bf9b4f4b-8e63-43fd-a73c-3e2d3748b451}}"
+----
+====
+
+This approach will return the username field of the database secret with version 'bf9b4f4b-8e63-43fd-a73c-3e2d3748b451' or admin in case the secret doesn't exist or the version doesn't exist.
+
+For the moment we are not considering the rotation function if any are applied, but it is in the work to be done.
+
+The only requirement is adding the camel-aws-secrets-manager jar to your Camel application.
+
+=== Testing AWS Secrets Manager Property Function with Localstack
+
+For testing purpose you might want to test the function on Localstack. To make this easier you can use the following two properties in combination with the others:
+
+[source,properties]
+----
+camel.vault.aws.overrideEndpoint = true
+camel.vault.aws.uriEndpointOverride = <localstack_url>
+----
+
+With this you could be able to retrieve secret with the function directly from the Localstack instance.
+
+=== Automatic Camel context reloading on Secret Refresh
+
+Being able to reload Camel context on a Secret Refresh could be done by specifying the usual credentials (the same used for AWS Secret Manager Property Function).
+
+With Environment variables:
+
+[source,bash]
+----
+export CAMEL_VAULT_AWS_USE_DEFAULT_CREDENTIALS_PROVIDER=accessKey
+export CAMEL_VAULT_AWS_REGION=region
+----
+
+or as plain Camel main properties:
+
+[source,properties]
+----
+camel.vault.aws.useDefaultCredentialProvider = true
+camel.vault.aws.region = region
+----
+
+Or by specifying accessKey/SecretKey and region, instead of using the default credentials provider chain.
+
+To enable the automatic refresh, you'll need additional properties to set:
+
+[source,properties]
+----
+camel.vault.aws.refreshEnabled=true
+camel.vault.aws.refreshPeriod=60000
+camel.vault.aws.secrets=Secret
+camel.main.context-reload-enabled = true
+----
+
+where `camel.vault.aws.refreshEnabled` will enable the automatic context reload, `camel.vault.aws.refreshPeriod` is the interval of time between two different checks for update events and `camel.vault.aws.secrets` is a regex representing the secrets we want to track for updates.
+
+Note that `camel.vault.aws.secrets` is not mandatory: if not specified the task responsible for checking updates events will take into accounts or the properties with an `aws:` prefix.
+
+=== Automatic Camel context reloading on Secret Refresh with Eventbridge and AWS SQS Services
+
+Another option is to use AWS EventBridge in conjunction with the AWS SQS service.
+
+On the AWS side, the following resources need to be created:
+
+- an AWS Couldtrail trail
+- an AWS SQS Queue
+- an Eventbridge rule of the following kind
+
+[source,json]
+----
+{
+  "source": ["aws.secretsmanager"],
+  "detail-type": ["AWS API Call via CloudTrail"],
+  "detail": {
+    "eventSource": ["secretsmanager.amazonaws.com"]
+  }
+}
+----
+
+This rule will make the event related to AWS Secrets Manager filtered
+
+- You need to set the a Rule target to the AWS SQS Queue for Eventbridge rule
+
+- You need to give permission to the Eventbrige rule, to write on the above SQS Queue. For doing this you'll need to define a json file like this:
+
+[source,json]
+----
+{
+    "Policy": "{\"Version\":\"2012-10-17\",\"Id\":\"<queue_arn>/SQSDefaultPolicy\",\"Statement\":[{\"Sid\": \"EventsToMyQueue\", \"Effect\": \"Allow\", \"Principal\": {\"Service\": \"events.amazonaws.com\"}, \"Action\": \"sqs:SendMessage\", \"Resource\": \"<queue_arn>\", \"Condition\": {\"ArnEquals\": {\"aws:SourceArn\": \"<eventbridge_rule_arn>\"}}}]}"
+}
+----
+
+Change the values for queue_arn and eventbridge_rule_arn, save the file with policy.json name and run the following command with AWS CLI
+
+[source,bash]
+----
+aws sqs set-queue-attributes --queue-url <queue_url> --attributes file://policy.json
+----
+
+where queue_url is the AWS SQS Queue URL of the just created Queue.
+
+Now you should be able to set up the configuration on the Camel side. To enable the SQS notification add the following properties:
+
+[source,properties]
+----
+camel.vault.aws.refreshEnabled=true
+camel.vault.aws.refreshPeriod=60000
+camel.vault.aws.secrets=Secret
+camel.main.context-reload-enabled = true
+camel.vault.aws.useSqsNotification=true
+camel.vault.aws.sqsQueueUrl=<queue_url>
+----
+
+where queue_url is the AWS SQS Queue URL of the just created Queue.
+
+Whenever an event of PutSecretValue for the Secret named 'Secret' will happen, a message will be enqueued in the AWS SQS Queue and consumed on the Camel side and a context reload will be triggered.
+
+
+=== Secrets Manager Producer operations
+
+Camel-AWS-Secrets-manager component provides the following operation on the producer side:
+
+- listSecrets
+- createSecret
+- deleteSecret
+- describeSecret
+- rotateSecret
+- getSecret
+- batchGetSecret
+- updateSecret
+- replicateSecretToRegions
+
+== Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+*pom.xml*
+
+[source,xml]
+---------------------------------------
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-aws-secrets-manager</artifactId>
+    <version>${camel-version}</version>
+</dependency>
+---------------------------------------
+
+where `$\{camel-version}` must be replaced by the actual version of Camel.
+
+
+=== Using AWS Secrets Manager Property Function in Spring Boot for Early resolving properties
+
+AWS Secrets Manager Spring Boot component starter offers the ability to early resolve properties, so the end user could resolve properties directly in the application.properties before both Spring Boot runtime and Camel context will start.
+
+This could be accomplished in the following way. You should specified this property in your application.properties file:
+
+[source,bash]
+----
+camel.component.aws-secrets-manager.early-resolve-properties=true
+----
+
+This will enable the feature so you'll be able to resolved properties, in your application.properties file, like:
+
+[source,bash]
+----
+foo = aws:database/prod#password
+----
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-security-hub-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-security-hub-component.adoc
new file mode 100644
index 000000000000..1aef282d4f83
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws-security-hub-component.adoc
@@ -0,0 +1,239 @@
+= AWS Security Hub Component
+:doctitle: AWS Security Hub
+:shortname: aws-security-hub
+:artifactid: camel-aws-security-hub
+:description: Manage and interact with AWS Security Hub for security findings.
+:since: 4.18
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Only producer is supported
+//Manually maintained attributes
+:group: AWS
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The AWS Security Hub component allows you to interact with
+https://aws.amazon.com/security-hub/[AWS Security Hub] to manage security findings.
+
+AWS Security Hub provides a comprehensive view of your security state in AWS and helps you check your environment against security industry standards and best practices.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Security Hub. More information is available at
+https://aws.amazon.com/security-hub/[Amazon Security Hub].
+
+== URI Format
+
+----
+aws-security-hub://label[?options]
+----
+
+You can append query options to the URI in the following format:
+
+`?options=value&option2=value&...`
+
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+== Usage
+
+=== Static credentials, Default Credential Provider and Profile Credentials Provider
+
+You have the possibility of avoiding the usage of explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
+
+The order of evaluation for Default Credentials Provider is the following:
+
+ - Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+ - Environment variables - `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
+ - Web Identity Token from AWS STS.
+ - The shared credentials and config files.
+ - Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is set.
+ - Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by specifying the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
+
+Only one of static, default and profile credentials could be used at the same time.
+
+For more information about this you can look at https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html[AWS credentials documentation]
+
+=== AWS Security Hub Producer operations
+
+Camel-AWS Security Hub component provides the following operation on the producer side:
+
+- batchImportFindings
+- getFindings
+- batchUpdateFindings
+- getFindingHistory
+- describeHub
+- listEnabledProductsForImport
+
+==== BatchImportFindings
+
+Import security findings into Security Hub. This is the primary way to send findings from custom integrations.
+
+._Java-only: uses inline Processor with AWS SDK builder API_
+[source,java]
+----
+from("direct:importFindings")
+    .process(exchange -> {
+        AwsSecurityFinding finding = AwsSecurityFinding.builder()
+            .schemaVersion("2018-10-08")
+            .id("my-finding-id")
+            .productArn("arn:aws:securityhub:us-east-1:123456789012:product/123456789012/default")
+            .generatorId("my-generator")
+            .awsAccountId("123456789012")
+            .types("Software and Configuration Checks/Vulnerabilities/CVE")
+            .createdAt("2024-01-15T00:00:00.000Z")
+            .updatedAt("2024-01-15T00:00:00.000Z")
+            .severity(Severity.builder().label(SeverityLabel.HIGH).build())
+            .title("Critical vulnerability found")
+            .description("A critical vulnerability was detected")
+            .resources(Resource.builder()
+                .type("AwsEc2Instance")
+                .id("arn:aws:ec2:us-east-1:123456789012:instance/i-1234567890abcdef0")
+                .build())
+            .build();
+        exchange.getIn().setBody(List.of(finding));
+    })
+    .to("aws-security-hub://findings?operation=batchImportFindings")
+    .to("mock:result");
+----
+
+==== GetFindings
+
+Retrieve security findings from Security Hub with optional filtering.
+
+._Java-only: uses inline Processor with AWS SDK builder API_
+[source,java]
+----
+from("direct:getFindings")
+    .process(exchange -> {
+        AwsSecurityFindingFilters filters = AwsSecurityFindingFilters.builder()
+            .severityLabel(StringFilter.builder()
+                .comparison(StringFilterComparison.EQUALS)
+                .value("CRITICAL")
+                .build())
+            .build();
+        exchange.getIn().setHeader(SecurityHubConstants.FILTERS, filters);
+        exchange.getIn().setHeader(SecurityHubConstants.MAX_RESULTS, 10);
+    })
+    .to("aws-security-hub://findings?operation=getFindings")
+    .to("mock:result");
+----
+
+==== BatchUpdateFindings
+
+Update security findings with notes, severity changes, workflow status, etc.
+
+._Java-only: uses inline Processor with AWS SDK builder API and Java constants_
+[source,java]
+----
+from("direct:updateFindings")
+    .process(exchange -> {
+        List<AwsSecurityFindingIdentifier> identifiers = List.of(
+            AwsSecurityFindingIdentifier.builder()
+                .id("my-finding-id")
+                .productArn("arn:aws:securityhub:us-east-1:123456789012:product/123456789012/default")
+                .build()
+        );
+        exchange.getIn().setHeader(SecurityHubConstants.FINDING_IDENTIFIERS, identifiers);
+
+        NoteUpdate note = NoteUpdate.builder()
+            .text("Reviewed and confirmed as false positive")
+            .updatedBy("security-team")
+            .build();
+        exchange.getIn().setHeader(SecurityHubConstants.NOTE, note);
+
+        WorkflowUpdate workflow = WorkflowUpdate.builder()
+            .status(WorkflowStatus.RESOLVED)
+            .build();
+        exchange.getIn().setHeader(SecurityHubConstants.WORKFLOW, workflow);
+    })
+    .to("aws-security-hub://findings?operation=batchUpdateFindings")
+    .to("mock:result");
+----
+
+==== DescribeHub
+
+Get information about the Security Hub configuration in your account.
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:describeHub")
+    .to("aws-security-hub://hub?operation=describeHub")
+    .to("mock:result");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:describeHub"/>
+  <to uri="aws-security-hub://hub?operation=describeHub"/>
+  <to uri="mock:result"/>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:describeHub
+      steps:
+        - to:
+            uri: aws-security-hub://hub
+            parameters:
+              operation: describeHub
+        - to:
+            uri: mock:result
+----
+====
+
+=== OCSF Integration
+
+AWS Security Hub uses the https://schema.ocsf.io/[Open Cybersecurity Schema Framework (OCSF)] for findings. You can use the Camel OCSF DataFormat to work with security events in a vendor-neutral format, then convert them for import into Security Hub.
+
+._Java-only: uses inline Processor with class literal and method reference_
+[source,java]
+----
+from("direct:ocsfToSecurityHub")
+    .unmarshal().ocsf(DetectionFinding.class)
+    .process(exchange -> {
+        DetectionFinding ocsf = exchange.getIn().getBody(DetectionFinding.class);
+        // Convert OCSF finding to AWS Security Finding format
+        AwsSecurityFinding finding = convertToAwsFinding(ocsf);
+        exchange.getIn().setBody(List.of(finding));
+    })
+    .to("aws-security-hub://findings?operation=batchImportFindings");
+----
+
+== Dependencies
+
+Maven users will need to add the following dependency to their pom.xml.
+
+*pom.xml*
+
+[source,xml]
+----
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-aws-security-hub</artifactId>
+    <version>${camel-version}</version>
+</dependency>
+----
+
+where `$\{camel-version}` must be replaced by the actual version of Camel.
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws2-athena-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws2-athena-component.adoc
new file mode 100644
index 000000000000..75b14a9dc4e7
--- /dev/null
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/aws2-athena-component.adoc
@@ -0,0 +1,976 @@
+= AWS Athena Component
+:doctitle: AWS Athena
+:shortname: aws2-athena
+:artifactid: camel-aws2-athena
+:description: Access AWS Athena.
+:since: 3.4
+:supportlevel: Stable
+:tabs-sync-option:
+:component-header: Only producer is supported
+//Manually maintained attributes
+:group: AWS
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The AWS2 Athena component supports running queries with https://aws.amazon.com/athena/[AWS Athena] and working with results.
+
+Prerequisites
+
+You must have a valid Amazon Web Services developer account, and be
+signed up to use Amazon Athena.  More information is available at
+https://aws.amazon.com/athena/[AWS Athena].
+
+== URI Format
+
+----
+aws2-athena://label[?options]
+----
+
+You can append query options to the URI in the following format: `?options=value&option2=value&...`
+
+
+// component options: START
+include::partial$component-configure-options.adoc[]
+include::partial$component-endpoint-options.adoc[]
+include::partial$component-endpoint-headers.adoc[]
+// component options: END
+
+Required Athena component options
+
+You have to provide the amazonAthenaClient in the
+Registry or your accessKey and secretKey to access
+the https://aws.amazon.com/athena/[AWS Athena] service.
+
+== Examples
+
+=== Producer Examples
+
+For example, to run a simple query, wait up to 60 seconds for completion, and log the results:
+
+[tabs]
+====
+Java::
++
+[source,java]
+----
+from("direct:start")
+    .setBody(constant("SELECT 1"))
+    .to("aws2-athena://label?waitTimeout=60000&outputLocation=s3://bucket/path/")
+    .to("aws2-athena://label?operation=getQueryResults&outputType=StreamList")
+    .split(body()).streaming()
+    .to("log:out")
+    .to("mock:result");
+----
+
+XML::
++
+[source,xml]
+----
+<route>
+  <from uri="direct:start"/>
+  <setBody>
+    <constant>SELECT 1</constant>
+  </setBody>
+  <to uri="aws2-athena://label?waitTimeout=60000&amp;outputLocation=s3://bucket/path/"/>
+  <to uri="aws2-athena://label?operation=getQueryResults&amp;outputType=StreamList"/>
+  <split streaming="true">
+    <simple>${body}</simple>
+    <to uri="log:out"/>
+    <to uri="mock:result"/>
+  </split>
+</route>
+----
+
+YAML::
++
+[source,yaml]
+----
+- route:
+    from:
+      uri: direct:start
+      steps:
+        - setBody:
+            constant: SELECT 1
+        - to:
+            uri: aws2-athena://label
+            parameters:
... 188314 lines suppressed ...