camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-4541) Bean Binding should support interface methods for non-public classes
Date Sat, 15 Oct 2011 10:15:12 GMT

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

Claus Ibsen resolved CAMEL-4541.
--------------------------------

    Resolution: Fixed

Thanks for the patch.

A good solution to fallback and use the interfaces for private class beans.
                
> Bean Binding should support interface methods for non-public classes
> --------------------------------------------------------------------
>
>                 Key: CAMEL-4541
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4541
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Mathieu Lalonde
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.9.0
>
>         Attachments: CAMEL-4541.tar
>
>
> As a user, I'd like to be able to use bean binding for non public classes.
> Bean binding is a strong selling point for Camel so it would be nice to have it work
for non-public classes as well, provided that the target method is available via an implemented
interface.
> eg.
> {code}
> // return private implementation of FooInterface
> FooInterface foo = Foos.newInstance();
> // works fine with plain java
> foo.doStuff("Hello");
> ...
> // This will throw an exception at runtime stating that the method can't be invoked (Illegal
Access)
> from("direct:start").bean(foo, "doStuff").mock("direct:result");
> {code}
> The Bean component should at the very least prefer interface methods (which won't cause
the above exception) to class methods when a matching method is available on both the class
and its interfaces (it currently ignore interface methods).
> On a side note, its probably faster to look for interface methods first since there are
usually less of them.
> I'll attach a unit test and patch soon.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message