[
https://issues.apache.org/activemq/browse/CAMEL-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52079#action_52079
]
Claus Ibsen commented on CAMEL-1663:
------------------------------------
Camel 1.x *before* fix
{code}
[ main] ClassPathXmlApplicationContext INFO Bean
'org.springframework.transaction.annotation.AnnotationTransactionAttributeSource#0'
is not eligible for getting processed by all BeanPostProcessors (for example:
not eligible for auto-proxying)
[ main] ClassPathXmlApplicationContext INFO Bean
'org.springframework.transaction.config.internalTransactionAdvisor' is not
eligible for getting processed by all BeanPostProcessors (for example: not
eligible for auto-proxying)
[ main] DefaultCamelContext INFO JMX
enabled. Using InstrumentationLifecycleStrategy.
[ main] ClassPathXmlApplicationContext INFO Bean
'annotatedRoute' is not eligible for getting processed by all
BeanPostProcessors (for example: not eligible for auto-proxying)
[ main] DriverManagerDataSource INFO Loaded
JDBC driver: org.hsqldb.jdbcDriver
[ main] ClassPathXmlApplicationContext INFO Bean
'dataSource' is not eligible for getting processed by all BeanPostProcessors
(for example: not eligible for auto-proxying)
[ main] ClassPathXmlApplicationContext INFO Bean
'txManager' is not eligible for getting processed by all BeanPostProcessors
(for example: not eligible for auto-proxying)
[ main] ClassPathXmlApplicationContext INFO Bean
'PROPAGATION_REQUIRED' is not eligible for getting processed by all
BeanPostProcessors (for example: not eligible for auto-proxying)
[ main] ClassPathXmlApplicationContext INFO Bean
'camel' is not eligible for getting processed by all BeanPostProcessors (for
example: not eligible for auto-proxying)
[ main] ClassPathXmlApplicationContext INFO Bean
'camel' is not eligible for getting processed by all BeanPostProcessors (for
example: not eligible for auto-proxying)
{code}
Camel 2.0 *after* fix:
{code}
2009-06-05 12:36:31,711 [main ] INFO ClassPathXmlApplicationContext
- Bean factory for application context
[org.springframework.context.support.classpathxmlapplicationcont...@5c98f3]:
org.springframework.beans.factory.support.defaultlistablebeanfact...@75db37
2009-06-05 12:36:31,802 [main ] INFO ClassPathXmlApplicationContext
- Bean
'org.springframework.transaction.annotation.AnnotationTransactionAttributeSource#0'
is not eligible for getting processed by all BeanPostProcessors (for example:
not eligible for auto-proxying)
2009-06-05 12:36:31,809 [main ] INFO ClassPathXmlApplicationContext
- Bean 'org.springframework.transaction.config.internalTransactionAdvisor' is
not eligible for getting processed by all BeanPostProcessors (for example: not
eligible for auto-proxying)
{code}
Notice that with the fix all the beans used by the application as such can be
post processed.
In Camel 1.x many of the beans *cannot* be.
> 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.5.0, 1.6.0, 2.0-M1, 1.6.1
> Reporter: Martin Gilday
> Assignee: Claus Ibsen
> Fix For: 2.0-M2
>
> 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.
