This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git
The following commit(s) were added to refs/heads/main by this push:
new aa5e856a chore: fix outdated facts on the trust, what-is, camel-dna,
tooling and team pages (#1835)
aa5e856a is described below
commit aa5e856a41c9af5d6ff5a07cd00b72f4b522302b
Author: Claus Ibsen <[email protected]>
AuthorDate: Sun Oct 25 12:59:58 2026 +0100
chore: fix outdated facts on the trust, what-is, camel-dna, tooling and
team pages (#1835)
* chore: fix outdated facts on the trust, what-is, camel-dna and tooling
pages
Trust page:
- 280+ releases (282 release tags); the bug record is dated June 2026
(it said "only 6 bugs are open today"); 11,600+ Stack Overflow
questions (it said 11,700+ answers; the source counts questions);
78-96% of commits by the core team, as the who-maintains table shows;
the 4.14 backports are in the past tense; the benchmark machine is a
64 GB Mac mini.
What-is and camel-dna pages:
- 83,000+ commits and 1,500+ contributors, as on the home page; median
bug fix time of 1 day; open bugs dated June 2026.
- The original Camel 1.0 route is from("test-jms:queue:test.queue"),
as the full listing on camel-dna shows.
- The tribute example moved to connect-service/camel-1-tribute in
camel-jbang-examples; the camel run command gave a 404.
Tooling page: the TUI is described for development, and its source
editor handles YAML, Java and XML and checks as you type (4.23).
Forage works with the Camel CLI.
Blog: Camel 1.0 shipped in 2007, not January 2009; the benchmark
machine is a Mac mini; the tribute example link. Support page: a broken
logging link.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m
* chore: team page - the committer list matches ASF LDAP
- Four IDs fixed against ASF LDAP: fmariani (was croway), tcunning (was
cunningt), nferraro (was nicolaferraro), marat (was mgubaidullin).
- Two blank IDs filled: jpoth and jamesnetherton.
- The 25 committers in LDAP who were missing are added, with the name
from LDAP. Their organisation is left empty, for them to fill in.
- Arno Noordover is a committer now, so he moves from the contributors
list to the committer list.
- The committer list is sorted by name, as the page asks. It has 97
committers, the same as LDAP.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m
---------
Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
---
content/blog/2026/06/camel-dna-19-years/index.md | 4 +-
.../camel-local-model-benchmark-round-2/index.md | 2 +-
.../2026/09/camel-local-model-benchmark/index.md | 6 +-
content/camel-dna/_index.md | 10 +-
content/community/support.md | 2 +-
content/community/team.md | 174 ++++++++++++---------
content/trust/_index.md | 16 +-
content/what-is-apache-camel/_index.md | 8 +-
data/tooling.yaml | 2 +-
layouts/tooling/list.html | 10 +-
10 files changed, 129 insertions(+), 105 deletions(-)
diff --git a/content/blog/2026/06/camel-dna-19-years/index.md
b/content/blog/2026/06/camel-dna-19-years/index.md
index f9bd406f..8cdc55ab 100644
--- a/content/blog/2026/06/camel-dna-19-years/index.md
+++ b/content/blog/2026/06/camel-dna-19-years/index.md
@@ -133,7 +133,7 @@ Every component — whether it's JMS (2007), Kafka (2014), or
LangChain4j (2024)
The Enterprise Integration Patterns from Hohpe and Woolf's
[book](https://www.enterpriseintegrationpatterns.com/) mapped perfectly to the
`Processor` chain. Every pattern — splitter, aggregator, content-based router,
wire tap — was just a `Processor` that manipulated an `Exchange`. The component
model meant adding JBI, CXF, or SOAP support didn't require touching the core.
-**Camel 1.0** shipped January 2009. **Camel 2.0** followed just 7 months later
in August 2009. The 2.x line would run for a decade — 26 minor releases.
+**Camel 1.0** shipped in 2007. **Camel 2.0** followed two years later, in
August 2009. The 2.x line would run for a decade — 26 minor releases.
### Era 2: Cloud and Big Data (2011–2018)
@@ -328,7 +328,7 @@ camel run *
No Maven project. No manual component wiring. No embedded broker — just `camel
infra run artemis` to start one in a container. The route reads from
`jms:queue:test.queue` and writes to `file://test`, exactly like the original.
-[Run the Camel 1.0 Tribute example
→](https://github.com/apache/camel-jbang-examples/tree/main/camel-1-tribute)
+[Run the Camel 1.0 Tribute example
→](https://github.com/apache/camel-jbang-examples/tree/main/connect-service/camel-1-tribute)
## Why It Lasted
diff --git a/content/blog/2026/09/camel-local-model-benchmark-round-2/index.md
b/content/blog/2026/09/camel-local-model-benchmark-round-2/index.md
index 718999fb..d9d5c63b 100644
--- a/content/blog/2026/09/camel-local-model-benchmark-round-2/index.md
+++ b/content/blog/2026/09/camel-local-model-benchmark-round-2/index.md
@@ -10,7 +10,7 @@ preview: "The second round of the local-model benchmark moved
from thirteen begi
Two weeks ago we [let a frontier model coach a small local model through
Camel](/blog/2026/09/camel-local-model-benchmark/) and fixed Camel between
every run: twelve of thirteen beginner examples in the end, and 99 findings
that were wrong for humans too. That post ended with a promise: the next runs
use a different set of examples, so the fixes land in the parts of Camel the
first thirteen did not reach.
-This is that round. Same laptop, same 22 GB local model (`qwen3.6:35b-a3b` in
Ollama), same frontier model running the harness and reading every failed
attempt, Camel 4.23 on the main branch. What changed is the examples, the way
the model is asked to work, and 31 more things in Camel.
+This is that round. Same Mac mini, same 22 GB local model (`qwen3.6:35b-a3b`
in Ollama), same frontier model running the harness and reading every failed
attempt, Camel 4.23 on the main branch. What changed is the examples, the way
the model is asked to work, and 31 more things in Camel.
## A more realistic example set
diff --git a/content/blog/2026/09/camel-local-model-benchmark/index.md
b/content/blog/2026/09/camel-local-model-benchmark/index.md
index d5aa964b..2aff9260 100644
--- a/content/blog/2026/09/camel-local-model-benchmark/index.md
+++ b/content/blog/2026/09/camel-local-model-benchmark/index.md
@@ -5,10 +5,10 @@ draft: false
authors: [davsclaus]
categories: ["AI", "Tooling"]
keywords: ["apache camel", "AI", "local model", "ollama", "coding agent",
"MCP", "camel cli", "yaml dsl", "validation", "error messages", "camel 4.23"]
-preview: "A frontier model ran the harness, a 22 GB local model on a laptop
did the work, and Camel was what we changed between runs: from 0 to 12 of 13
beginner examples over twenty runs, and 99 of the findings were wrong for
humans too. All of it ships in Camel 4.23."
+preview: "A frontier model ran the harness, a 22 GB local model on a Mac mini
did the work, and Camel was what we changed between runs: from 0 to 12 of 13
beginner examples over twenty runs, and 99 of the findings were wrong for
humans too. All of it ships in Camel 4.23."
---
-Everyone claims their tool "works with any LLM". We wanted a number instead of
a claim, so we measured two very different models on the same Camel tasks, on
one laptop, with the same tooling. Then we did something more useful than
reporting the score: we ran the weaker model twenty times over two days, and
between every run we fixed whatever in Camel had made it fail.
+Everyone claims their tool "works with any LLM". We wanted a number instead of
a claim, so we measured two very different models on the same Camel tasks, on
one Mac mini, with the same tooling. Then we did something more useful than
reporting the score: we ran the weaker model twenty times over two days, and
between every run we fixed whatever in Camel had made it fail.
The interesting result is not which model won. It is that nearly everything
the losing model tripped over was a problem in Camel, an unclear message or a
tool that did not say what to write, that would have tripped up a person as
well.
@@ -152,7 +152,7 @@ Twelve of 117 are about a small model's particular
weaknesses: things a frontier
## What it means
-A frontier model with Camel's tools builds the beginner examples from one
sentence each. A local model on a laptop got there too, once Camel told it what
to write instead of only what was wrong: twelve of thirteen, in a third of the
tokens and less than half the time of the first attempt.
+A frontier model with Camel's tools builds the beginner examples from one
sentence each. A local model on a Mac mini got there too, once Camel told it
what to write instead of only what was wrong: twelve of thirteen, in a third of
the tokens and less than half the time of the first attempt.
The Camel side of that ships in Camel 4.23, and none of it is an AI feature.
Better messages from the Simple parser, the YAML loader and the runtime; a
validator that says what to write; catalog tools that answer the question
asked; a schema that requires what the runtime requires. And one thing we did
not go looking for: validating every YAML example in the EIP documentation, 71
of 280 failed. They all pass in 4.23, the build now checks them, and the
component pages are next ([CAMEL-246 [...]
diff --git a/content/camel-dna/_index.md b/content/camel-dna/_index.md
index 35ac52ff..e175e156 100644
--- a/content/camel-dna/_index.md
+++ b/content/camel-dna/_index.md
@@ -106,11 +106,11 @@ No Maven project. No build step. No manual wiring. Just
one YAML file and one co
| **Dependencies** | Declared in pom.xml | Auto-downloaded |
| **Components** | 19 | 350+ |
| **Patterns (EIPs)** | ~20 | 65+ |
-| **Contributors** | A handful | 1,600+ |
+| **Contributors** | A handful | 1,500+ |
| **Lines of code** | Tens of thousands | Millions |
{{< /table >}}
-What stayed the same: **`from("jms:queue:test.queue").to("file://test")`**
+What stayed the same: **`from("test-jms:queue:test.queue").to("file://test")`**
The core routing idea — take data from here, transform it if needed, send it
there — is unchanged. It's the DNA of every Camel route ever written, from a
simple file transfer to a complex multi-system integration handling billions of
messages.
@@ -125,12 +125,12 @@ We recreated the original Camel 1.0 example as a modern
Camel CLI example. Run i
camel infra run artemis
# Run the tribute example
-camel run
https://github.com/apache/camel-jbang-examples/tree/main/camel-1-tribute
+camel run
https://github.com/apache/camel-jbang-examples/tree/main/connect-service/camel-1-tribute
```
It sends 10 test messages to a JMS queue and saves them to files — exactly
like the original, nearly two decades later.
-[See the tribute example on GitHub
→](https://github.com/apache/camel-jbang-examples/tree/main/camel-1-tribute)
+[See the tribute example on GitHub
→](https://github.com/apache/camel-jbang-examples/tree/main/connect-service/camel-1-tribute)
## The DNA
@@ -138,7 +138,7 @@ SQL has `SELECT * FROM`. Camel has `from().to()`.
Both are ideas so fundamental that they outlasted every technology shift
around them — new languages, new runtimes, new architectures, cloud,
containers, AI. The world changed; the abstraction didn't need to.
-Thousands of companies. Billions of messages. 350+ connectors. 65+ patterns.
100,000+ commits. 1,600+ contributors. Nearly two decades of production use.
+Thousands of companies. Billions of messages. 350+ connectors. 65+ patterns.
83,000+ commits. 1,500+ contributors. Nearly two decades of production use.
It all started with one line:
diff --git a/content/community/support.md b/content/community/support.md
index 333d4ce5..1dd1cf55 100644
--- a/content/community/support.md
+++ b/content/community/support.md
@@ -63,7 +63,7 @@ But not only that. Remember to also include information such
as:
* what platform and JDK?
* any particular container being used? and if so, what version?
* stack traces generally really help! (Remember to post which version of
Camel you use, this is important to know when posting stacktraces.) If in
doubt, include the whole thing; often exceptions get wrapped in other
exceptions and the exception right near the bottom explains the actual error,
not the first few lines at the top. It's very easy for us to skim-read past
unnecessary parts of a stack trace.
-* log output can be useful too; sometimes [enabling DEBUG logging]
(/manual/faq/how-do-i-change-the-logging.html) can help
+* log output can be useful too; sometimes enabling DEBUG logging for the
`org.apache.camel` package can help
* your code & configuration files are often useful
* did it work before? what have you changed to break it?
* try upgrading to the latest release and see if it's fixed there
diff --git a/content/community/team.md b/content/community/team.md
index a89b861f..3c37cf6e 100644
--- a/content/community/team.md
+++ b/content/community/team.md
@@ -7,80 +7,105 @@ This page lists who we are. By all means add yourself to the
list. Let's sort it
## Committers
{{< table >}}
-| Name | ID | Organisation |
-|------------------------|------------------|----------------------------|
-| Aaron Mulder | ammulder | Chariot Solutions |
-| Akitoshi Yoshida | ay | SAP |
-| Andrea Cosentino | acosentino | IBM |
-| Antonin Stefanutti | astefanutti | Red Hat |
-| Babak Vahdat | bvahdat | Cyberlogic Consulting |
-| Ben O'Day | boday | Initek Consulting |
-| Bilgin Ibryam | bibryam | |
-| Bob Paulin | bob | |
-| Bruce Snyder | bsnyder | |
-| Charles Moulliard | cmoulliard | IBM |
-| Christian Mueller | cmueller | Amazon Web Services |
-| Christian Posta | ceposta | Solo |
-| Christian Schneider | cschneider | |
-| Claus Ibsen | davsclaus | IBM |
-| Colm O hEigeartaigh | coheigea | Talend |
-| David Jencks | djencks | IBM |
-| Daniel Kulp | dkulp | Talend |
-| Denis Istomin | distomin | |
-| Dmitry Volodin | dmvolod | T-Systems RUS |
-| Federico Mariani | croway | IBM |
-| Franz Forsthofer | forsthofer | SAP |
-| Freeman Fang | ffang | IBM |
-| Gary Tully | gtully | IBM |
-| Gert Vanthienen | gertv | |
-| Gregor Zurowski | gzurowski | Independent consultant |
-| Guillaume Nodet | gnodet | IBM |
-| Hadrian Zbarcea | hadrian | |
-| Henryk Konsek | hekonsek | |
-| Hiram Chirino | chirino | Red Hat |
-| Ioannis Canellos | iocanel | IBM |
-| Jacek Laskowski | jlaskowski | |
-| James Carman | jcarman | Savoir Technologies |
-| Jan Bednar | janbednar | CGI IT Czech Republic |
-| Jean-Baptiste Onofré | jbonofre | |
-| Jeff Genender | jgenender | Savoir Technologies |
-| Jeremy Ross | jeremyross | Elevation Solutions |
-| Johan Edstrom | joed | Savoir Technologies |
-| John Poth | | IBM |
-| Jonathan Anstey | janstey | IBM |
-| James Netherton | | IBM |
-| James Strachan | jstrachan | |
-| Karen Lease | klease | |
-| Luca Burgazzoli | lburgazzoli | Red Hat |
-| Marat Gubaidullin | mgubaidullin | Talisman Cloud |
-| Martin Krasser | krasserm | |
-| Nicky Sandhu | nsandhu | |
-| Nicola Ferraro | nicolaferraro | Redpanda |
-| Onder Sezgin | onders | |
-| Omar Al-Safi | oalsafi | |
-| Otavio Rodolfo Piske | orpiske | IBM |
-| Quinn Stevenson | quinn | |
-| Raul Kripalani | raulk | |
-| Pascal Schumacher | pascalschumacher | |
-| Pasquale Congiusti | pcongiusti | IBM |
-| Peter Palaga | ppalaga | IBM |
-| Rhuan Rocha | rhuanrocha | Digibee |
-| Rich Newcomb | rnewcomb | |
-| Richard Kettelerij | rickette | Avisi BV |
-| Rob Davies | rajdavies | |
-| Roman Kalukiewicz | romkal | |
-| Scott England-Sullivan | sully6768 | Red Hat |
-| Stan Lewis | slewis | Red Hat |
-| Tadayoshi Sato | tsato | IBM |
-| Thomas Diesler | tdiesler | IBM |
-| Tom Cunningham | cunningt | IBM |
-| Tomohisa Igarashi | igarashitm | IBM |
-| Tracy Snell | tjsnell | Juice Labs |
-| Willem Jiang | ningjiang | Huawei |
-| William Tam | wtam | Red Hat |
-| Zineb Bendhiba | zbendhiba | IBM |
-| Zheng Feng | zhfeng | Red Hat |
-| Zoran Regvart | zregvart | |
+| Name | ID | Organisation |
+|--------------------------------|------------------|------------------------|
+| Aaron Mulder | ammulder | Chariot Solutions |
+| Adriano Machado | amachado | |
+| Akitoshi Yoshida | ay | SAP |
+| Alex Dettinger | aldettinger | |
+| Andrea Cosentino | acosentino | IBM |
+| Andrea Tarocchi | valdar | |
+| Antonin Stefanutti | astefanutti | Red Hat |
+| Arno Noordover | anoordover | het CAK |
+| Ashwin J. Karpe | akarpe | |
+| Aurélien Pupier | apupier | |
+| Babak Vahdat | bvahdat | Cyberlogic Consulting |
+| Ben O'Day | boday | Initek Consulting |
+| Bilgin Ibryam | bibryam | |
+| Bob Paulin | bob | |
+| Bruce Snyder | bsnyder | |
+| Charles Moulliard | cmoulliard | IBM |
+| Christian Mueller | cmueller | Amazon Web Services |
+| Christian Posta | ceposta | Solo |
+| Christian Schneider | cschneider | |
+| Christoph Deppisch | cdeppisch | |
+| Claudio Miranda | claudio4j | |
+| Claus Ibsen | davsclaus | IBM |
+| Colm O hEigeartaigh | coheigea | Talend |
+| Daniel Kulp | dkulp | Talend |
+| David Jencks | djencks | IBM |
+| David Valeri | dvaleri | |
+| Denis Istomin | distomin | |
+| Dhiraj Sureshkumar Bokde | dhirajsb | |
+| Dmitry Volodin | dmvolod | T-Systems RUS |
+| Federico Mariani | fmariani | IBM |
+| Franz Forsthofer | forsthofer | SAP |
+| Freeman Fang | ffang | IBM |
+| Gaelle Fournier | gfournier | |
+| Gary Tully | gtully | IBM |
+| Gert Vanthienen | gertv | |
+| Gregor Zurowski | gzurowski | Independent consultant |
+| Grzegorz Grzybek | ggrzybek | |
+| Guillaume Nodet | gnodet | IBM |
+| Hadrian Zbarcea | hadrian | |
+| Henryk Konsek | hekonsek | |
+| Hiram Chirino | chirino | Red Hat |
+| Ioannis Canellos | iocanel | IBM |
+| Ivan Kulaga | kulagaivan | |
+| Jacek Laskowski | jlaskowski | |
+| James Carman | jcarman | Savoir Technologies |
+| James Netherton | jamesnetherton | IBM |
+| James Strachan | jstrachan | |
+| Jan Bednar | janbednar | CGI IT Czech Republic |
+| Jean-Baptiste Onofré | jbonofre | |
+| Jeff Genender | jgenender | Savoir Technologies |
+| Jeremy Ross | jeremyross | Elevation Solutions |
+| Jiří Ondrušek | jiriondrusek | |
+| Johan Edstrom | joed | Savoir Technologies |
+| John Poth | jpoth | IBM |
+| Jonathan Anstey | janstey | IBM |
+| Jono Morris | jono | |
+| Karen Lease | klease | |
+| Kengo Seki | sekikn | |
+| Luca Burgazzoli | lburgazzoli | Red Hat |
+| Luigi De Masi | ldemasi | |
+| Marat Gubaidullin | marat | Talisman Cloud |
+| Marcin Grzejszczak | mgrzejszczak | |
+| Maria Arias de Reyna Dominguez | delawen | |
+| Martin Krasser | krasserm | |
+| Nicky Sandhu | nsandhu | |
+| Nicola Ferraro | nferraro | Redpanda |
+| Nicolas Filotto | nfilotto | |
+| Omar Al-Safi | oalsafi | |
+| Omar Atie | atiaomar | |
+| Onder Sezgin | onders | |
+| Otavio Rodolfo Piske | orpiske | IBM |
+| Pascal Schumacher | pascalschumacher | |
+| Pasquale Congiusti | pcongiusti | IBM |
+| Peter Palaga | ppalaga | IBM |
+| Quinn Stevenson | quinn | |
+| Ramu K | ramu12 | |
+| Raul Kripalani | raulk | |
+| Rhuan Rocha | rhuanrocha | Digibee |
+| Rich Newcomb | rnewcomb | |
+| Richard Kettelerij | rickette | Avisi BV |
+| Rob Davies | rajdavies | |
+| Roman Kalukiewicz | romkal | |
+| Scott England-Sullivan | sully6768 | Red Hat |
+| Sergey Beryozkin | sergeyb | |
+| Stan Lewis | slewis | Red Hat |
+| Stephan Siano | siano | |
+| Tadayoshi Sato | tsato | IBM |
+| Thomas Diesler | tdiesler | IBM |
+| Tom Cunningham | tcunning | IBM |
+| Tomohisa Igarashi | igarashitm | IBM |
+| Tracy Snell | tjsnell | Juice Labs |
+| Vignesh Nayak Manel | vmanel | |
+| Willem Jiang | ningjiang | Huawei |
+| William Tam | wtam | Red Hat |
+| Zheng Feng | zhfeng | Red Hat |
+| Zineb Bendhiba | zbendhiba | IBM |
+| Zoran Regvart | zregvart | |
{{< /table >}}
### Contributors
@@ -99,7 +124,6 @@ Then you can get in touch with the Camel team from the
[Mailing Lists](../mailin
| Andy Depue | |
| Axel Hohaus | |
| Arjan Moraal | |
-| Arno Noordover | het CAK |
| Ashish Nayyar | |
| Bahaa Zaid | |
| Barry Kaplan | |
diff --git a/content/trust/_index.md b/content/trust/_index.md
index 591a5fac..9efb6a6c 100644
--- a/content/trust/_index.md
+++ b/content/trust/_index.md
@@ -51,7 +51,7 @@ than years. Designated **Long Term Support (LTS)** releases
receive bug and secu
to a year, giving you a stable target you can plan around. We treat backward
compatibility as a
feature: the rare breaking change is always documented in the
[Migration and Upgrade](/manual/migration-and-upgrade.html) guide, so an
upgrade never holds a
-surprise. The data backs this up: [272 releases over 19 years with zero
gaps](/blog/2026/06/camel-always-on/)
+surprise. The data backs this up: [280+ releases over 19 years with zero
gaps](/blog/2026/06/camel-always-on/)
and a core API so stable that [code from the first commit in 2007 still
compiles unchanged](/blog/2026/06/camel-dna-19-years/).
<p>
@@ -105,7 +105,7 @@ follows.
Each one costs work you never see: triage against the [Security
Model](/manual/security-model.html),
a fix with regression tests, a CVE assignment, and a written, signed advisory
carrying the affected
version ranges and a workaround you can apply today — and then the backport.
**26 of those 32 fixes
-were carried all the way back to the 4.14.x LTS line**, so teams on the older
LTS get them without a
+were carried all the way back to the 4.14.x LTS line**, so teams on the older
LTS got them without a
major upgrade. None of it becomes public until the fixes have shipped, and we
publish even when a
hardening change has no known exploit path — because the alternative is asking
you to trust a silence
you cannot check. For the full timeline and the process behind the July 2026
batch — including two
@@ -134,7 +134,7 @@ it away from you. Development happens entirely in the open
on public mailing lis
anyone is free to read the code, propose a change, review a release, or verify
a fix for
themselves. The numbers tell the story: [1,500+ contributors from 450+
companies across 20+ countries](/blog/2026/06/camel-by-the-numbers/).
And behind those contributors, the [same core engineering
team](/blog/2026/07/camel-who-maintains/)
-has maintained Camel since 2009 — through multiple acquisitions — contributing
80–95% of all
+has maintained Camel since 2009 — through multiple acquisitions — contributing
78–96% of all
commits every single year. When you hit a bug in a component written ten years
ago, the person
who wrote it is likely still an active committer.
@@ -203,10 +203,10 @@ major release.
## A proven bug fix track record
-The community has fixed [7,070 out of 7,081 reported
bugs](/blog/2026/06/camel-bug-fix-track-record/)
+When we counted in June 2026, the community had fixed [7,070 out of 7,081
reported bugs](/blog/2026/06/camel-bug-fix-track-record/)
— a **99.8% resolution rate** — with a median fix time of **1 day**. That
track record has been
-sustained for 17 of the last 19 years across 350+ connectors and 272
production releases. Only 6
-bugs are open today. When something breaks, it gets fixed fast, and the data
is there to prove it.
+sustained for 17 of the last 19 years across 350+ connectors and 272
production releases, and only 6
+bugs were open at the time. When something breaks, it gets fixed fast, and the
data is there to prove it.
<p>
<a class="button dark" href="/blog/2026/06/camel-bug-fix-track-record/">See
the data</a>
@@ -300,7 +300,7 @@ are logged as warnings so existing applications are not
broken.
AI coding assistants are remarkably good at Apache Camel — and it is not an
accident. [Nineteen
years of stable APIs](/blog/2026/06/camel-ai-trained/) mean training data does
not go stale,
-11,700+ Stack Overflow answers provide real-world examples, and a predictable
component model
+11,600+ Stack Overflow questions provide real-world examples, and a
predictable component model
lets LLMs generalize across 350+ connectors. Add a built-in [MCP
server](/manual/camel-jbang-mcp.html),
machine-readable catalog metadata, a schema-validated YAML DSL, and dedicated
[AI integration patterns](/components/next/eips/ai-patterns.html) for building
AI-powered
@@ -308,7 +308,7 @@ routes, and Camel is one of the best-trained integration
frameworks for AI-assis
We measure that rather than claim it. Given the Camel CLI as tools, a frontier
model
[built all 13 beginner examples](/blog/2026/09/camel-local-model-benchmark/)
from a one-line
-description each. A 22 GB local model running on a laptop went from 0 of 13
with a bare prompt to
+description each. A 22 GB local model running on a 64 GB Mac mini went from 0
of 13 with a bare prompt to
12 of 13 once it had the Camel MCP server and error messages that say what to
write — and 99 of
the 117 things it tripped over along the way were wrong for people too, so
they were fixed for
everyone and ship in Camel 4.23. It works in the other direction as well: for
the 4.22 LTS
diff --git a/content/what-is-apache-camel/_index.md
b/content/what-is-apache-camel/_index.md
index 7a713dd5..7eed9bd4 100644
--- a/content/what-is-apache-camel/_index.md
+++ b/content/what-is-apache-camel/_index.md
@@ -111,7 +111,7 @@ These aren't theoretical — they're production-tested
patterns used by thousand
## The origin story
-The very first Camel route ever written was
`from("jms:queue:test.queue").to("file://test")` — one line, June 2007. Nearly
two decades later, that same idea powers every Camel route: take data from
here, send it there. The framework grew from 19 components to 350+, from a
handful of contributors to 1,500+ — but the DNA never changed.
+The example that shipped with Camel 1.0 was
`from("test-jms:queue:test.queue").to("file://test")` — one line, June 2007.
Nearly two decades later, that same idea powers every Camel route: take data
from here, send it there. The framework grew from 19 components to 350+, from a
handful of contributors to 1,500+ — but the DNA never changed.
**[Read the full origin story — Camel DNA →](/camel-dna/)**
@@ -135,10 +135,10 @@ Camel also provides an **MCP server** (Model Context
Protocol) that connects AI
| **Connectors** | 350+ |
| **Integration patterns** | 65+ |
| **Contributors** | 1,500+ |
-| **Commits** | 100,000+ |
+| **Commits** | 83,000+ |
| **Years in production** | Nearly two decades |
-| **Median bug fix time** | 1–2 days |
-| **Open bugs** | Typically 10 or fewer (across 350+ connectors) |
+| **Median bug fix time** | 1 day |
+| **Open bugs** | 6 in June 2026 (across 350+ connectors) |
| **License** | Apache License 2.0 — free, no cost, forever |
{{< /table >}}
diff --git a/data/tooling.yaml b/data/tooling.yaml
index 3c034c8b..7271117b 100644
--- a/data/tooling.yaml
+++ b/data/tooling.yaml
@@ -141,4 +141,4 @@ toolGroups:
desc: >-
Opinionated bean factories for Apache Camel — configure data
sources, connection factories, AI models, and more via
- properties. Works with Camel JBang, Spring Boot, and Quarkus.
+ properties. Works with the Camel CLI, Spring Boot, and Quarkus.
diff --git a/layouts/tooling/list.html b/layouts/tooling/list.html
index efd4643a..7ad40cbc 100644
--- a/layouts/tooling/list.html
+++ b/layouts/tooling/list.html
@@ -37,11 +37,11 @@
<div>
<h2 id="tui">Camel TUI</h2>
<p class="tooling-section-intro">
- The <code>camel tui</code> command launches a full
terminal-based
- UI with route status, message flow, and tracing in a single
view
- — plus a built-in mini source editor for YAML DSL routes with
- context-aware Tab completion, validation on save, and inline
- quick docs.
+ The <code>camel tui</code> command launches a terminal-based UI
+ for development, with route status, message flow, and tracing
in
+ a single view — plus a built-in source editor for YAML, Java
and
+ XML routes that checks them as you type, with context-aware Tab
+ completion and inline quick docs.
</p>
<p class="tooling-section-intro">
See the <a href="{{ $data.tuiDocs }}">Camel TUI
documentation</a> for more details.
