camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Gredler (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4704) Allow type converters to be specified as Spring beans
Date Wed, 23 Nov 2011 05:44:40 GMT


Daniel Gredler commented on CAMEL-4704:

Here's another related bug, also marked "won't fix": CAMEL-3746

I've been looking at the code, and it appears that the change would involve a small tweak
to AbstractCamelContextFactoryBean.afterPropertiesSet(), probably adding another small code
block in the area where we already query the registry for event notifiers, endpoint strategies,
intercept strategies and lifecycle strategies.
> Allow type converters to be specified as Spring beans
> -----------------------------------------------------
>                 Key: CAMEL-4704
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.8.2
>            Reporter: Daniel Gredler
>            Priority: Minor
> There are many Camel configuration elements that are auto-discovered when they are configured
as Spring beans (Tracer, InterceptStrategy, EventNotifier, PlatformTransactionManager, etc):
> However, instances of TypeConverter are not auto-discovered based on the Spring configuration
(there is a different auto-discovery mechanism):
> A related JIRA ticket (requesting custom XML syntax) was marked "won't fix": CAMEL-1685.
> I agree that the extra XML tag is not necessary. However, the omission of Spring bean
auto-discovery seems to violate the principle of least surprise -- as a new Camel user, knowing
that Camel auto-discovers Spring beans for other configuration elements, I was surprised to
find that Camel didn't find my TypeConverter Spring bean.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message