[
https://issues.jboss.org/browse/AS7-4610?page=com.atlassian.jira.plugin.s...
]
Christoph Gutmann commented on AS7-4610:
----------------------------------------
{code}org.jboss.as.ejb3.deployment.processors.ViewInterfaces.getPotentialViewInterfaces(Class<?>
beanClass){code} does only get potential view interfaces of the concrete class, not
it's superclass
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira