You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/08/12 15:31:47 UTC

[jira] Created: (CAMEL-3050) RouteBuilderRef should work out of the box with Spring 3 and dependency injection

RouteBuilderRef should work out of the box with Spring 3 and dependency injection
---------------------------------------------------------------------------------

                 Key: CAMEL-3050
                 URL: https://issues.apache.org/activemq/browse/CAMEL-3050
             Project: Apache Camel
          Issue Type: Bug
          Components: camel-spring
    Affects Versions: 2.4.0
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
             Fix For: 2.5.0


Spring 3 changed internally how dependency resolution works. Its now worse as we have to play tricks in the Camel namespace handler to tell Camel the various pieces you can ref, should depend on Camel. Otherwise the dependency resolution in Spring is not working properly.

This used to work like a charm in Spring 2.5.6.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (CAMEL-3050) RouteBuilderRef should work out of the box with Spring 3 and dependency injection

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/activemq/browse/CAMEL-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-3050.
--------------------------------

    Resolution: Fixed

trunk: 984775.

> RouteBuilderRef should work out of the box with Spring 3 and dependency injection
> ---------------------------------------------------------------------------------
>
>                 Key: CAMEL-3050
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3050
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-spring
>    Affects Versions: 2.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.5.0
>
>
> Spring 3 changed internally how dependency resolution works. Its now worse as we have to play tricks in the Camel namespace handler to tell Camel the various pieces you can ref, should depend on Camel. Otherwise the dependency resolution in Spring is not working properly.
> This used to work like a charm in Spring 2.5.6.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.