camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Poth (JIRA)" <>
Subject [jira] [Commented] (CAMEL-10573) Align FallbackTypeConverter loading in OSGI environments
Date Mon, 12 Dec 2016 18:49:58 GMT


John Poth commented on CAMEL-10573:

Hi [~davsclaus],

Thanks for looking into this!

So this PR aligns the way FallbackTypeConverters are loaded in [Camel-OSGI|]
and in [plain|]
Camel. As you can see there is no annotation check in the latter.

I didn't remove the other annotation check you mentioned because it is in line with what plain
Camel [does|].

The motivation behind this alignment is that, in Camel/OSGI, Camel-jackson's [FallbackTypeConverter|]
is not loaded. This is best illustrated by the added [test|]
in my PR. As there was no TypeConverter testing, I created my own (may be a good base to test
other TypeConverters?).

I'd be happy to propose other solutions if alignment doesn't seem like a good idea :)



> Align FallbackTypeConverter loading in OSGI environments
> --------------------------------------------------------
>                 Key: CAMEL-10573
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: osgi
>            Reporter: John Poth
>            Assignee: John Poth
> In a OSGI environment only, FallBackTypeConverters are [required|]
to be annotated with @Converter whereas otherwise they are [not|].
> This causes [camel-jackson's|]
FallbackTypeConverter to not be loaded and a 'NoTypeConversionAvailableException' will be
> I will provide a PR.

This message was sent by Atlassian JIRA

View raw message