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 2009/06/02 15:52:50 UTC

[jira] Commented: (CAMEL-1663) Spring BeanPostProcessors do not work on beans which are used in Camel route builders

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

Claus Ibsen commented on CAMEL-1663:
------------------------------------

This is a hard one to get fixed.

Namespace handlers in Spring is like a 2nd class citizen so the CamelBeanPostProcessor is not registered like the regular post processors as its done from a namespace handler. And then Spring just goes blank and denies running post processors as the initial number of post processors != current number of post processors.

Then you get the dreadful 'bean X is not eligible for post processing'.

Its kinda like a catch-22 situation. I got a few more ideas to find a solution.

> Spring BeanPostProcessors do not work on beans which are used in Camel route builders 
> --------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1663
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1663
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-spring
>    Affects Versions: 1.6.0, 2.0-M1
>            Reporter: Martin Gilday
>            Assignee: Claus Ibsen
>         Attachments: camel-1663.zip
>
>
> Spring PostProcessors stop working for beans which are injected into Camel route builders.  See attached test cases showing processor breaks as soon as injected into a route builder.

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