[OWB-586] Interceptors added by portable extensions don't work

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.1.1
• Component/s: Interceptor and Decorators
• Labels: tck
• Assignee: Mark Struberg
• Reporter: Rohit Dilip Kelapure
• Created: 14/Jun/11 15:51
• Updated: 30/Aug/11 09:27
• Resolved: 03/Aug/11 14:49

Description

The CDI Spec says "During the application initialization process, the container fires a series of events, allowing portable extensions to integrate with the container initialization process".
In OWB, Interceptors added programatically during these lifecycle events are NOT added to our interceptor stack in org.apache.webbeans.portable.events.discovery.AfterBeanDiscoveryImpl.addBean(Bean<?>).

In org.apache.webbeans.portable.events.discovery.AfterBeanDiscoveryImpl.addBean(Bean<?>) we create a CustomInterceptor that wraps the passed interceptor. We then add this CustomInterceptor to a set of org.apache.webbeans.container.BeanManagerImpl.webBeansInterceptors.

Unfortunately multiple CustomInterceptor instances evaluate to the same hashcode and different interceptors overwrite one another when they get added to the Set. Consequently the right set of interceptors does not fire when a managed bean is to be intercepted.

The fix to this issue is for CustomInterceptor and WebBeansInterceptor to override the default equals and hashcode methods.

This bug causes 6 tests of the org.jboss.jsr299.tck.tests.interceptors.definition.custom.CustomInterceptorTest to FAIL.