felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clement Escoffier (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FELIX-3012) "Duplicate name&signature" problem
Date Fri, 08 Jul 2011 08:09:16 GMT

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

Clement Escoffier updated FELIX-3012:

    Assignee: Clement Escoffier


Thanks to Guillaume Sauthier, I was able to reproduce the issue with:
public class ClusterDaemon {

    private ArrayList ControlledServersNames;

    public ArrayList getControlledServersNames() {
        return null;

There is a name conflict when iPOJO generates the getter of the field and the interceptor
of the method. So, as you stated in the description, modifying the name of the field fixes
the issue. I will have a look.

> "Duplicate name&signature" problem
> ----------------------------------
>                 Key: FELIX-3012
>                 URL: https://issues.apache.org/jira/browse/FELIX-3012
>             Project: Felix
>          Issue Type: Bug
>          Components: iPOJO
>    Affects Versions: iPOJO-1.6.0, iPOJO-1.8.0
>         Environment: Ubuntu Linux 2.6.32
>            Reporter: Miguel González
>            Assignee: Clement Escoffier
>             Fix For: ipojo-manipulator-1.8.2
> Using iPOJO, i stumbled upon a problem involving one of my components. When I tried to
instantiate it, the JVM threw an exception saying that there was some "duplicate name&signature".
After countless hours of hopeless search, I found by chance that I had getters and setters
misspelled: instead of 'getAttName' I had 'getattName', so I believe that the iPOJO class
processing creates methods that matched my misspelled ones, which lead to this coincidence.
After I fixed the method names, everything worked as expected.
> I hope this info can be useful for anyone who has the same problem.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message