camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (CAMEL-651) BeanProcessor more intelligent choosing of correct method (AOP proxies problems)
Date Mon, 30 Jun 2008 07:14:00 GMT

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

Claus Ibsen reassigned CAMEL-651:
---------------------------------

    Assignee: Claus Ibsen

> 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.5.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.


Mime
View raw message