[jboss-jira] [JBoss JIRA] Resolved: (JBMETA-305) @Local and @Remote annotation processors should not pick up interfaces of super class of bean class

[jaikiran pai (JIRA)]

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

jaikiran pai resolved JBMETA-305.
---------------------------------

    Fix Version/s: jboss-metadata-ejb-2.0.0-alpha-21
       Resolution: Done


> @Local and @Remote annotation processors should not pick up interfaces of super class of bean class
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBMETA-305
>                 URL: https://jira.jboss.org/browse/JBMETA-305
>             Project: JBoss Metadata
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: ejb
>    Affects Versions: jboss-metadata-ejb-2.0.0-alpha-20
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>             Fix For: jboss-metadata-ejb-2.0.0-alpha-21
>
>
> Consider these EJBs:
> @Stateless
> public class BaseBean implements A
> {
> ...
> }
> @Local
> public interface A
> {...
> }
> @Stateless
> public class ChildBean extends BaseBean implements B
> {
> ...
> }
> @Local
> public interface B
> {
> ...
> }
> In this case, the ChildBean is expected to expose just B as the local business view. It should _not_ expose A as the local business view. 
> However, our current annotation processors currently don't handle this scenario which breaks the EJB3.1 spec which says:
> "4.9.2.1 Session Bean Superclasses:
> A session bean class is permitted to have superclasses that are themselves session bean classes. However, there are no special rules that apply to the processing of annotations or the deployment descriptor for this case. For the purposes of processing a particular session bean class, all superclass processing is identical regardless of whether the superclasses are themselves session bean classes. In this regard, the use of session bean classes as superclasses merely represents a convenient use of implementation inheritance, but does not have component inheritance semantics.
> As an example, the client views exposed by a particular session bean are not inherited by a subclass that also happens to define a session bean.
> @Stateless
> public class A implements Foo { ... }
> @Stateless
> public class B extends A implements Bar { ... }
> Assuming Foo and Bar are local business interfaces and there is no associated deployment descriptor, session bean A exposes local business interface Foo and session bean B exposes local business interface Bar, but not Foo."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira