[forge-issues] [JBoss JIRA] (ROASTER-91) Add JavaInterfaceMethodImpl class

[George Gastaldi (JIRA)]

     [ https://issues.jboss.org/browse/ROASTER-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Gastaldi closed ROASTER-91.
----------------------------------
    Resolution: Won't Fix


I've been thinking a bit about this and I think we don't want to mess around with the JavaInterfaceMethod behavior for now as this may introduce some undesirable side effects.

> Add JavaInterfaceMethodImpl class
> ---------------------------------
>
>                 Key: ROASTER-91
>                 URL: https://issues.jboss.org/browse/ROASTER-91
>             Project: Roaster
>          Issue Type: Bug
>    Affects Versions: 2.18.0.Final
>            Reporter: Nicolas Challut
>            Assignee: Nicolas Challut
>
> method "bar" should be overrided in javaClass but it is empty.
> While searching in the code, I found that :
> {code}
> for (Method method : source.getMethods())
>       {
>          if (method.isAbstract() && !target.hasMethod(method))
>          {
> {code}
> It seems that in JavaInterfaceSource the method aren't abstract by default (in the standars, interface method is abstract, key word is redundant).
> So, I see 2 ways to resolve this :
> # Change JavaInterface implementation to set all method abstract without add the key word
> # Change Methods#implementAbstractMethod() to handle JavaInterfaceSource type (if source instance of JavaInterfaceSource, addAll() )
> What do you guys think about it ?
> UPDATE 21/01 : We could add a new class which extend MethodImpl to handle special behavior of interface.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)