You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2026/05/13 05:42:00 UTC
[jira] [Assigned] (CAMEL-23302) camel-xslt - In dev mode then we could have contentCache=false to make it possible to update xslt live
[ https://issues.apache.org/jira/browse/CAMEL-23302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-23302:
-----------------------------------
Assignee: Adriano Machado
> camel-xslt - In dev mode then we could have contentCache=false to make it possible to update xslt live
> ------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-23302
> URL: https://issues.apache.org/jira/browse/CAMEL-23302
> Project: Camel
> Issue Type: Improvement
> Components: camel-xslt
> Reporter: Claus Ibsen
> Assignee: Adriano Machado
> Priority: Major
> Fix For: 4.21.0
>
>
> When you use jbang in --dev mode and have a XSLT file and do data mapping, you may want to change the XSLT file, but camel does not trigger a full route reload as its not a route file that was changed. But the xslt component can have contentCache=false to load the XSLT from disk so it will work in --dev mode where you can just change the XSLT file live.
>
> There are other components that has contentCache option (resource based) so we can make this more general for those as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)