[
https://issues.apache.org/jira/browse/CAMEL-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794203#comment-16794203
]
Claus Ibsen edited comment on CAMEL-13313 at 3/16/19 10:29 AM:
---------------------------------------------------------------
An idea could be to create a new camel-fasttypeconverter as it would be faster
as both loading the type converters and also invoking them as there is no
reflection via java method calls. Then we just detect that this is on the
classpath and Camel will use it (you can of course explicit configure it too).
Another idea is to drop the old way of type converters and use this as default.
And then maybe have a option you can turn on, to add support for the old way,
to scan for legacy type converters.
was (Author: davsclaus):
An idea could be to create a new camel-fasttypeconverter as it would be faster
as both loading the type converters and also invoking them as there is no
reflection via java method calls
> camel-core - Add alternative way of loading type converters without classpath
> scanning
> --------------------------------------------------------------------------------------
>
> Key: CAMEL-13313
> URL: https://issues.apache.org/jira/browse/CAMEL-13313
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.0.0, 3.0.0-M2
>
>
> We should make it possible to load and install all type converters without
> having to do
> - classpath scanning
> - loading TypeConverter file from META-INF
> For example we do some apt compiler source code generation for the core type
> converter.
> It would be good to have something similar or other means of loading and
> installing type converters that can be done fast and quick, which is needed
> for Camel K and graal like runtimes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
