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 2022/09/02 14:46:00 UTC

[jira] [Resolved] (CAMEL-14573) camel-core - TypeConverter scanning for @Converter should be in its own JAR

     [ https://issues.apache.org/jira/browse/CAMEL-14573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-14573.
---------------------------------
    Resolution: Won't Fix

> camel-core - TypeConverter scanning for @Converter should be in its own JAR
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-14573
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14573
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Priority: Major
>             Fix For: 3.x
>
>
> We can move the logic for Camel 2.x style @Converter annotation scanning to its own JAR and outside camel-core / camel-core-engine so you need to opt-in to enable this.
> Today you need to set a flag on camel context to enable this. But instead we can have it as a JAR on classpath. Then the code is outside camel-core and we avoid a bit of complexity to support both the new fast style via source code generated loaders vs old style.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)