[
https://issues.apache.org/activemq/browse/CAMEL-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43829#action_43829
]
Claus Ibsen commented on CAMEL-651:
-----------------------------------
This issue can be closed, however would be nice with an exclude list of known
AOP proxy methods. But its not a show stopper to cut a new 1.4.0 RC
> BeanProcessor more intelligent choosing of correct method (AOP proxies
> problems)
> --------------------------------------------------------------------------------
>
> Key: CAMEL-651
> URL: https://issues.apache.org/activemq/browse/CAMEL-651
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 1.4.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 1.4.0
>
>
> The example: example-spring-jms using AOP proxies as a part of the enhancer
> server demonstration to do somekind of audit tracking using aspectj and
> spring.
> However Camel now have trouble picking the correct method (broken in later
> 1.4-SNAPSHOT) or as the AOP proxied object now has an removeAdvisor(int)
> method that Camel think it can invoke also.
> However the BeanInfo#chooseMethodWithMatchingBody method doens't consider the
> MEP pattern (InOut etc). So when there is an Out pattern the method should
> not be void.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
