camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CAMEL-12293) Avoid KeyAlreadyExistsException in ManagedTypeConverterRegistry.listTypeConverters()
Date Tue, 27 Feb 2018 10:38:00 GMT


ASF GitHub Bot commented on CAMEL-12293:

jamesnetherton commented on issue #2239: CAMEL-12293: Avoid KeyAlreadyExistsException for
listTypeConverters JMX operation
   Thanks for the feedback. I pushed a simple duplicate check onto master.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Avoid KeyAlreadyExistsException in ManagedTypeConverterRegistry.listTypeConverters()
> ------------------------------------------------------------------------------------
>                 Key: CAMEL-12293
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: James Netherton
>            Assignee: James Netherton
>            Priority: Minor
> There is a JMX operation on the TypeConverterRegisty to fetch a list of converters.
> The TabularData object that's returned is keyed on the 'from' type name and 'to' type
name. This mostly works ok. But you could have multiple converters which handle the same 'from'
and 'to' types. In this case a KeyAlreadyExistsException exception is thrown when adding CompositeData
to TabularData.
> We could avoid this by using a simple 'index' field in the CompositeData ,which could
just be a simple number we increment each time around the type converter list loop.

This message was sent by Atlassian JIRA

View raw message