This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch quick-fix/home-and-llms-facts in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit 353647acc93f1ef6d33e77f32332d70bc23dd0a9 Author: Claus Ibsen <[email protected]> AuthorDate: Sun Oct 25 11:34:11 2026 +0100 chore: fix the Semantic language example in the 4.23 release post The example had no expert and put instructions and criteria directly on the evaluation. It fails validation against main, and in 4.23 an evaluation without an expert fails at startup. It now names its expert (and says how to register it) and puts instructions and criteria under parameters, as the documentation shows. It validates with Camel 4.23.0 and with main. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m --- content/blog/2026/10/camel423-whatsnew/index.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/content/blog/2026/10/camel423-whatsnew/index.md b/content/blog/2026/10/camel423-whatsnew/index.md index cf4c95ff..208977ae 100644 --- a/content/blog/2026/10/camel423-whatsnew/index.md +++ b/content/blog/2026/10/camel423-whatsnew/index.md @@ -170,17 +170,21 @@ endpoint, step id and exception. The event dev console shows these details. ## Semantic EIPs The new [Semantic](/components/next/languages/semantic-language.html) language lets a route make decisions on the meaning of a message. -You declare named evaluations once, and then use them anywhere Camel accepts an expression or predicate: +You declare named evaluations once, and then use them anywhere Camel accepts an expression or predicate. +Each evaluation names its *expert*, here a bean registered with +`camel.beans.decisions=#class:org.apache.camel.component.typesafeai.TypeSafeAiSemanticAdapter`: ```yaml - semantic: evaluation: department: + expert: decisions type: choice - instructions: Which department should handle this message? - criteria: - billing: Invoices, payments and refunds - technical: Bugs, outages and technical problems + parameters: + instructions: Which department should handle this message? + criteria: + billing: Invoices, payments and refunds + technical: Bugs, outages and technical problems - route: from: uri: direct:tickets
