[jboss-jira] [JBoss JIRA] (AS7-2574) setter declared in a superclass prevents SAR deployments from being deployed

[Jamie Webb (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/AS7-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649146#comment-12649146 ] 

Jamie Webb commented on AS7-2574:
---------------------------------

Looks to me like ClassReflectionIndex is broken and should be using getMethods() rather than getDeclaredMethods(). Doing otherwise violates basic OOP expectations. Spot-checking a few other uses of this class, I can see that several of them are tediously walking up the superclass chain as you describe. Why? This is standard Java behaviour, and JBoss is for some reason reimplementing it repeatedly and badly.
I rather suspect that those few other callers that are not reimplementing getMethods() on top of DeploymentReflectionIndex are just as broken as the SAR deployer.

If there's something wrong with getMethods(), please at least just reimplement it once, presumably in DeploymentReflectionIndex?

                
> setter declared in a superclass prevents SAR deployments from being deployed
> ----------------------------------------------------------------------------
>
>                 Key: AS7-2574
>                 URL: https://issues.jboss.org/browse/AS7-2574
>             Project: Application Server 7
>          Issue Type: Bug
>    Affects Versions: 7.0.2.Final
>         Environment: jdk1.6.0_29, win7 32bit, cygwin
>            Reporter: Radim Hanus
>            Assignee: Richard Opalka
>
> java.lang.IllegalStateException: No such set method for property 'xxx' found on class XXX
> is thrown when the property setter is not declared in bean class but superclass

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