You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2024/04/16 16:29:00 UTC
[jira] [Updated] (CAMEL-19779) camel-core: investigate externalizing large builtin texts
[ https://issues.apache.org/jira/browse/CAMEL-19779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated CAMEL-19779:
------------------------------------
Fix Version/s: 4.6.0
(was: 4.x)
> camel-core: investigate externalizing large builtin texts
> ---------------------------------------------------------
>
> Key: CAMEL-19779
> URL: https://issues.apache.org/jira/browse/CAMEL-19779
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 4.0.0, 4.1.0
> Reporter: Otavio Rodolfo Piske
> Assignee: Guillaume Nodet
> Priority: Major
> Labels: help-wanted
> Fix For: 4.6.0
>
>
> This is about a comment I raised here: https://github.com/apache/camel/pull/11181/files#r1302680683
> Long story short, we have lots of places in the code base where we generate large strings (i.e.: dump stuff to xml, json, java, SQL, etc) and we keep those strings builtin into the code base.
> From a readability and maintainability perspective this is extremely hard to maintain, debug and read. Ideally, we should investigate a way to externalize those strings. For some cases, we might need to find a templating solution that is suitable and acceptable for the project.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)