You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2019/06/14 08:57:00 UTC

[jira] [Commented] (CAMEL-13647) camel-main - Add support for auto binding to components by interface type and discover impl class on classpath

    [ https://issues.apache.org/jira/browse/CAMEL-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863849#comment-16863849 ] 

Claus Ibsen commented on CAMEL-13647:
-------------------------------------

The problem is to do a full classpath scanning where you don't know the package names, as this can be in any of the packages. So we need to find all the JARs on the classpath, and look inside them, to gather their package names. 

All of this comes with a performance penalty.

> camel-main - Add support for auto binding to components by interface type and discover impl class on classpath
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-13647
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13647
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.0.0, 3.0.0.M4
>
>
> This can make convention over configuration nicer. For example some components requires a ConnectionFactory etc and if we can auto-discover that on the classpath there is only 1 implementation of such interface, we can try to auto create the instance and configure it on the component.
> This should be an option you can turn on|off.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)