aldettinger commented on a change in pull request #2010:
URL: https://github.com/apache/camel-quarkus/pull/2010#discussion_r524487765
##########
File path: docs/modules/ROOT/pages/reference/extensions/jslt.adoc
##########
@@ -31,3 +31,49 @@ Please refer to the above link for usage and configuration
details.
----
Check the xref:user-guide/index.adoc[User guide] for more information about
writing Camel Quarkus applications.
+
+== allowContextMapAll option in native mode
+
+The `allowContextMapAll` option is not supported in native mode as it requires
reflective access to security sensitive camel core classes such as
+`CamelContext` & `Exchange`. This is considered a security risk and thus
access to the feature is not provided by default.
+
+== Additional Camel Quarkus configuration
+
+=== Using JSLT templates from classpath resource in native mode
+A trick is needed when using JSLT templates from classpath resources in native
mode. In such a situation, one needs to explicitly embed the resources in the
native executable by specifying the `include-patterns` option.
+
+For instance, the route below would load the JSLT schema from a classpath
resource named _transformation.json_:
+[source,java]
+----
+from("direct:start").to("jslt:transformation.json");
+----
+
+In order to work in native mode the `include-patterns` configuration should be
set. For instance, in the `application.properties` file as below :
+[source,properties]
+----
+quarkus.camel.native.resources.include-patterns = *.json
+----
+
+More information about selecting resources for inclusion in the native
executable could be found at
xref:user-guide/native-mode.adoc#embedding-resource-in-native-executable[Embedding
resource in native executable].
+
+=== Using JSLT functions in native mode
+When using JSLT functions from camel-quarkus in native mode, the classes
hosting the functions would need to be
link:https://quarkus.io/guides/writing-native-applications-tips#registering-for-reflection[registered
for reflection]. When registering the target function is not possible, one may
end up writing a stub as below.
Review comment:
Second thought welcome here, I have found no way to detect the native
classes at build time here.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
