This is an automated email from the ASF dual-hosted git repository.
aldettinger 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 a5f51b76 Fix some data extraction blog post statements as an issue was
discovered
a5f51b76 is described below
commit a5f51b76a0949152ddd8f0445e0ce4631d39038f
Author: aldettinger <aldettin...@gmail.com>
AuthorDate: Fri Sep 13 10:07:10 2024 +0200
Fix some data extraction blog post statements as an issue was discovered
---
content/blog/2024/09/data-extraction-example/index.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/content/blog/2024/09/data-extraction-example/index.md
b/content/blog/2024/09/data-extraction-example/index.md
index 7058702c..2eafce27 100644
--- a/content/blog/2024/09/data-extraction-example/index.md
+++ b/content/blog/2024/09/data-extraction-example/index.md
@@ -81,8 +81,9 @@ public interface CustomPojoExtractionService {
```
Furthermore, notice how we are using the `@org.apache.camel.Handler`
annotation to specify that Camel needs to invoke the `extractFromText` method.
-Logically, we should be able to use the full power of [the bean
binding](/manual/bean-binding.html), even with Quarkus LangChain4j AI services.
-Could you imagine injecting Camel headers and variables into the LLM prompt?
+Ideally, we should be able to use the full power of [the bean parameter
binding](/manual/bean-binding.html#_parameter_binding), even with Quarkus
LangChain4j AI services.
+However, there is an
[issue](https://github.com/quarkiverse/quarkus-langchain4j/issues/888) today.
+If a solution is found, then we could imagine injecting Camel headers and
variables into the LLM prompt.
Once the AI service is available in the registry, it's easy to invoke it from
a Camel route, for instance, as below:
