[weld-issues] [JBoss JIRA] Commented: (WELD-746) Observer inheritance should take into consideration EJB semantics

Tue Nov 2 09:42:01 EDT 2010

    [ https://jira.jboss.org/browse/WELD-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560834#action_12560834 ] 

Marius Bogoevici commented on WELD-746:
---------------------------------------

clarification: Weld considers the inherited methods as being observer methods, however, because they're not business methods according to the EJB spec, it can't invoke them properly. It shouldn't even try, only the business methods of a session bean can be observers.

> Observer inheritance should take into consideration EJB semantics
> -----------------------------------------------------------------
>
>                 Key: WELD-746
>                 URL: https://jira.jboss.org/browse/WELD-746
>             Project: Weld
>          Issue Type: Bug
>    Affects Versions: 1.1.0.Beta2
>            Reporter: Marius Bogoevici
>            Assignee: Pete Muir
>             Fix For: 1.1.0.Beta3
>
>
> This is illustrated in org.jboss.jsr299.tck.tests.event.observer.enterprise.EnterpriseEventInheritanceTest as of 1.0.2.CR3.
> In the affected version of Weld,  IndirectStockWatcher and LazyFarmer are expected to observe events. However, those classes are session beans, and the observer methods are not part of their business interface as defined by the EJB 3.1 spec (4.9.2.1 Session Bean superclasses: "the client views exposed by a particular session bean are not inherited by a subclass that also happens to define a session bean").
> This currently fails in JBoss AS trunk b/c of a proxy issue (in later revisions, the EjbDescriptor does not return the inherited interfaces as business interfaces, and the methods are not found on the session bean proxy).

-- 
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