[
https://issues.apache.org/jira/browse/CAMEL-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4704:
-------------------------------
Fix Version/s: Future
Issue Type: New Feature (was: Improvement)
> Allow type converters to be specified as Spring beans
> -----------------------------------------------------
>
> Key: CAMEL-4704
> URL: https://issues.apache.org/jira/browse/CAMEL-4704
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Affects Versions: 2.8.2
> Reporter: Daniel Gredler
> Priority: Minor
> Fix For: Future
>
>
> There are many Camel configuration elements that are auto-discovered when
> they are configured as Spring beans (Tracer, InterceptStrategy,
> EventNotifier, PlatformTransactionManager, etc):
> http://camel.apache.org/advanced-configuration-of-camelcontext-using-spring.html
> However, instances of TypeConverter are not auto-discovered based on the
> Spring configuration (there is a different auto-discovery mechanism):
> http://camel.apache.org/type-converter.html
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
