[
https://issues.apache.org/activemq/browse/CAMEL-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62693#action_62693
]
Mark Ford commented on CAMEL-3255:
----------------------------------
Thanks for implementing this and adding the xml support.
I'm just curious about your comment where you saw synchronization in the
default case. While both states for the DefaultTypeConverter required invoking
the accessing method at various times, only the strategy for the lazy load
implemented a synchronized method for accessing. The result is that there was
no synchronization for the default case.
> 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.
