[jboss-jira] [JBoss JIRA] (AS7-4610) Interface not found when deploying an EJB of class A that extends B and B implements an Interface

[Stuart Douglas (JIRA)]

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

Stuart Douglas commented on AS7-4610:
-------------------------------------

I am not 100% sure if this is a bug, the spec actually says:

If the bean does not expose any other business interfaces (Local, Remote) or No-Interface view, and the bean class implements a single interface, that interface is assumed to be the business interface of the bean.

Generally when the spec refers to 'the bean class' it actually means the EJB class, and not any super classes. The spec is not super clear on this I know, but I have a feeling that this may be tested in the TCK. I will investigate.
                
> Interface not found when deploying an EJB of class A that extends B and B implements an Interface
> -------------------------------------------------------------------------------------------------
>
>                 Key: AS7-4610
>                 URL: https://issues.jboss.org/browse/AS7-4610
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 7.1.1.Final
>            Reporter: Christoph Gutmann
>            Assignee: jaikiran pai
>
> The class hierarchy is as follows: 
> -class EJBClient extends class Client (POJO)
> -class Client implements interface MyInterface (POJO)
> When deploying EJB 'EJBClient', JBoss does not resolve indirectly implemented interface by an EJB via a superclass. This did work in JBoss5. When deploying such an EJB you get the error message
> {code}
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Bean class org.foo.EJBClient specifies @Local annotation, but does not implement 1 interface
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira