(camel-website) branch main updated: Remove broken links in removed components

[fm...@apache.org]

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

fmariani 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 df8be615 Remove broken links in removed components
df8be615 is described below

commit df8be615ea1eaec711804234fc71d31c8d2f6e36
Author: Croway <fe...@gmail.com>
AuthorDate: Fri Sep 5 10:33:13 2025 +0200

    Remove broken links in removed components
---
 content/blog/2024/12/langchain4j-bean-interface/index.md  | 4 ++--
 content/blog/2025/01/langchain4j-bean-name/index.md       | 4 ++--
 content/blog/2025/02/langchain-structured-output/index.md | 2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/content/blog/2024/12/langchain4j-bean-interface/index.md b/content/blog/2024/12/langchain4j-bean-interface/index.md
index 4720fcb0..ca418c2f 100644
--- a/content/blog/2024/12/langchain4j-bean-interface/index.md
+++ b/content/blog/2024/12/langchain4j-bean-interface/index.md
@@ -75,7 +75,7 @@ As always, there are manual [workarounds](https://quarkus.io/guides/cdi-referenc
 
 However, this kind of issues is best fixed in the Camel Quarkus LangChain4j extension itself.
 Indeed, this extension aims at solving as much as possible the intricacies of developing camel routes using high-level [AI services](https://docs.langchain4j.dev/tutorials/ai-services/).
-The good news is that the [AI service resolution by interface](/camel-quarkus/next/reference/extensions/langchain4j.html#extensions-langchain4j-configuration-resolving-ai-services-by-interface) has just been delivered with the recent [Camel Quarkus 3.17.0 release](/blog/2024/12/camel-quarkus-release-3.17.0/).
+The good news is that the AI service resolution by interface has just been delivered with the recent [Camel Quarkus 3.17.0 release](/blog/2024/12/camel-quarkus-release-3.17.0/).
 
 # Conclusion
 
@@ -84,5 +84,5 @@ Still experimentation after experimentation, we discover some intricacies and us
 Being able to resolve AI services by interface is just one of those goodness.
 There are actually more coming in future versions.
 That should be a good subject for a next blog post.
-Meanwhile, I would encourage the community to test out the [Camel Quarkus Langchain4j extension](/camel-quarkus/next/reference/extensions/langchain4j.html).
+Meanwhile, I would encourage the community to test out the Camel Quarkus Langchain4j extension.
 And please, as usual, feel welcome to report any bugs and improvements [here](https://github.com/apache/camel-quarkus/issues/new/choose).
diff --git a/content/blog/2025/01/langchain4j-bean-name/index.md b/content/blog/2025/01/langchain4j-bean-name/index.md
index dd0b79af..5d162190 100644
--- a/content/blog/2025/01/langchain4j-bean-name/index.md
+++ b/content/blog/2025/01/langchain4j-bean-name/index.md
@@ -70,7 +70,7 @@ From a Camel Quarkus point of view, it should become present in the coming relea
 
 # Conclusion
 
-In this article, we have seen yet another goodness of the [Camel Quarkus LangChain4j extension](/camel-quarkus/next/reference/extensions/langchain4j.html).
+In this article, we have seen yet another goodness of the Camel Quarkus LangChain4j extension.
 Camel users are used to invoke bean by name since years, so it really makes sense to also resolve AI services the same way.
-So, if you are on the path of exploring what AI  could bring to integration scenarios and not afraid to write a few lines of code, I would encourage you to test out the [Camel Quarkus Langchain4j extension](/camel-quarkus/next/reference/extensions/langchain4j.html).
+So, if you are on the path of exploring what AI  could bring to integration scenarios and not afraid to write a few lines of code, I would encourage you to test out the Camel Quarkus Langchain4j extension.
 Of course, feedbacks and contributions are welcome, so feel free to report any bugs and improvements [here](https://github.com/apache/camel-quarkus/issues/new/choose).
diff --git a/content/blog/2025/02/langchain-structured-output/index.md b/content/blog/2025/02/langchain-structured-output/index.md
index 6c416573..bb7c8cf2 100644
--- a/content/blog/2025/02/langchain-structured-output/index.md
+++ b/content/blog/2025/02/langchain-structured-output/index.md
@@ -133,5 +133,5 @@ So there is basically nothing the developer should worry about, structured outpu
 In this sense, this improvement comes almost for free.
 By making the LLM to adhere to a specific JSON schema, the data extraction accuracy is expected to raise up.
 Still, it would be good to find concrete benchmarks about impact on performance and accuracy.
-Anyway, it seems to be a good milestone on our journey toward using AI with the [Camel Quarkus Langchain4j extension](/camel-quarkus/next/reference/extensions/langchain4j.html).
+Anyway, it seems to be a good milestone on our journey toward using AI with the Camel Quarkus Langchain4j extension.
 By the way, feel welcome to play with it and report any bugs and improvements [here](https://github.com/apache/camel-quarkus/issues/new/choose).