[
https://issues.apache.org/activemq/browse/CAMEL-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62728#action_62728
]
Claus Ibsen commented on CAMEL-3255:
------------------------------------
Yeah
We love contributions so you are welcome to work on improved patch.
I can also see your point.
But my solution ensure all access to the type converter ensures the lazy
loading has occurred.
In your solution this check is buried in the code and you could potentially
miss a couple of checks and then its flawed.
As the type converter is a bottleneck in Camel we must ensure the default
setting is as fast as possible.
The lazy loading option is a niche feature.
> Add property to DefaultCamelContext to allow for lazy loading of the
> DefaultTypeConverter
> -----------------------------------------------------------------------------------------
>
> Key: CAMEL-3255
> URL: https://issues.apache.org/activemq/browse/CAMEL-3255
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Affects Versions: 2.2.0, 2.3.0, 2.4.0
> Reporter: Mark Ford
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.5.0
>
> Attachments: patch.txt
>
>
> The loading of type converters was changed from a lazy loading to an up front
> loading in a Camel 2.2. See issue CAMEL-2392 for details. Accordingly to the
> logging, it takes approximately 300 millis for this process to complete.
> The proposal is to allow the configuration of this loading strategy for cases
> where the initialization time of contexts is more important than the loading
> of type converters. The "lazyLoadTypeConverters" property on the context will
> default to false to preserve the current up front loading behavior as the
> default. If this value is set to true, then the loading of the type
> converters will happen when accessed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
