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 2014/04/16 16:44:19 UTC
[jira] [Resolved] (CAMEL-7361) would be nice if
org.apache.camel.spring.Main could take a system property or CLI option to
package scan classes too
[ https://issues.apache.org/jira/browse/CAMEL-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-7361.
--------------------------------
Resolution: Fixed
> would be nice if org.apache.camel.spring.Main could take a system property or CLI option to package scan classes too
> --------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-7361
> URL: https://issues.apache.org/jira/browse/CAMEL-7361
> Project: Camel
> Issue Type: Improvement
> Components: tooling
> Reporter: james strachan
> Assignee: Claus Ibsen
> Fix For: 2.13.1, 2.14.0
>
>
> Imagine you've some other beans you wanna initialise too in addition to a camel XML. I tried adding a few spring XML files in META-INF/spring/* but then I got an error if one of the spring XML files didn't have camel inside.
> So it'd be nice to either allow lots of spring XMLs to be used (and not all of them need camel); or allow some packages to be scanned for @Component / @Service annotations so that we can configure other beans in jars which are not necessarily camel related (e.g. to create some mbeans for monitoring/logging).
--
This message was sent by Atlassian JIRA
(v6.2#6252)