This is an automated email from the ASF dual-hosted git repository.
oscerd pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 10f750a2d61f CAMEL-24422: docs - add the camel-docling input-source
note to the 4.22 and 4.18 upgrade guides (#26013)
10f750a2d61f is described below
commit 10f750a2d61f52f39237675b23ca176002d8b443
Author: Andrea Cosentino <[email protected]>
AuthorDate: Fri Sep 4 09:44:18 2026 +0200
CAMEL-24422: docs - add the camel-docling input-source note to the 4.22 and
4.18 upgrade guides (#26013)
Document the camel-docling input-source opt-in (allowUrlSource /
allowFilePathSource / inputBaseDirectory)
in the 4.22.1 and 4.18.5 patch sections of the upgrade guide, keeping
main's version-specific guides in
sync with the maintenance branches.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
---
.../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 29 ++++++++++++++++++++++
.../ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 29 ++++++++++++++++++++++
2 files changed, 58 insertions(+)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
index accc42e81f52..64ac783abd68 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
@@ -13,6 +13,35 @@ See the xref:camel-upgrade-recipes-tool.adoc[documentation]
page for details.
== Upgrading from 4.18.4 to 4.18.5
+=== camel-docling
+
+A `String` message body is no longer interpreted as a location by default.
Previously the producer
+inspected the body and, when it started with `http://` or `https://`, handed
it to Docling as a remote
+URL to fetch; when it started with `/` or contained `\`, it read it from the
local filesystem; otherwise
+it converted it as document content.
+
+The two location readings must now be enabled explicitly:
+
+* `allowUrlSource` (default `false`) - interpret a body starting with
`http://` or `https://` as a URL.
+* `allowFilePathSource` (default `false`) - interpret a body starting with
`/`, or containing `\`, as a
+ local file path. This also covers the single directory-or-file `String` body
accepted by the batch
+ operations.
+
+A route that passes the document itself in the body is unaffected. A route
that passes a URL or a path in
+the body must set the matching option, otherwise the exchange fails with an
`IllegalArgumentException`
+naming the option to enable.
+
+The `CamelDoclingInputFilePath` header is unchanged and still accepts a path
without any opt-in, as are
+`File`, `byte[]` and `InputStream` bodies and the explicit path collections
(`List<String>`, `String[]`,
+`List<File>`, `File[]`) used by the batch operations.
+
+A new `inputBaseDirectory` option is also available. When set, every local
input path - from the header,
+from a file path body, and from the batch operations - must resolve inside
that directory once normalized.
+It is unset by default, which keeps the previous behaviour of accepting any
path.
+
+Additionally, a local input path that does not exist is now reported as a
`File not found` `IOException`
+before Docling is invoked. Previously the size check silently skipped a path
that resolved to nothing and
+the failure surfaced later, from the Docling process or API call.
=== camel-dynamic-router
The `dynamic-router-control` endpoint no longer takes the subscription
`predicate`, or the
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
index 519c54102036..553d1b1fdafa 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
@@ -13,6 +13,35 @@ See the xref:camel-upgrade-recipes-tool.adoc[documentation]
page for details.
== Upgrading from 4.22.0 to 4.22.1
+=== camel-docling
+
+A `String` message body is no longer interpreted as a location by default.
Previously the producer
+inspected the body and, when it started with `http://` or `https://`, handed
it to Docling as a remote
+URL to fetch; when it started with `/` or contained `\`, it read it from the
local filesystem; otherwise
+it converted it as document content.
+
+The two location readings must now be enabled explicitly:
+
+* `allowUrlSource` (default `false`) - interpret a body starting with
`http://` or `https://` as a URL.
+* `allowFilePathSource` (default `false`) - interpret a body starting with
`/`, or containing `\`, as a
+ local file path. This also covers the single directory-or-file `String` body
accepted by the batch
+ operations.
+
+A route that passes the document itself in the body is unaffected. A route
that passes a URL or a path in
+the body must set the matching option, otherwise the exchange fails with an
`IllegalArgumentException`
+naming the option to enable.
+
+The `CamelDoclingInputFilePath` header is unchanged and still accepts a path
without any opt-in, as are
+`File`, `byte[]` and `InputStream` bodies and the explicit path collections
(`List<String>`, `String[]`,
+`List<File>`, `File[]`) used by the batch operations.
+
+A new `inputBaseDirectory` option is also available. When set, every local
input path - from the header,
+from a file path body, and from the batch operations - must resolve inside
that directory once normalized.
+It is unset by default, which keeps the previous behaviour of accepting any
path.
+
+Additionally, a local input path that does not exist is now reported as a
`File not found` `IOException`
+before Docling is invoked. Previously the size check silently skipped a path
that resolved to nothing and
+the failure surfaced later, from the Docling process or API call.
=== camel-dynamic-router
The `dynamic-router-control` endpoint no longer takes the subscription
`predicate`, or the
