Hm... I did some source code research on this issue before creating this bug, and I do not understand how it can be glassfish fault since between Event.fire() method and call to "handle" method weld do a lot of work and some how does not invoke any interceptors. Call stack that I see looks like that:

EventImpl
BeanManagerImpl
ObserverMethodImpl
MethodInjectionsPoint
ForwardingWeldMethod
WeldMethodImpl
SecureReflections
SecureReflectionAccess
$$_WeldProxy (autogenerated)
ProxyMethodHandler
EnterpriseTargetBeanInstance
EnterpriseBeanProxy
SecureReflections
....
here starts java.reflect, and actual glassfish call stack

I thought that glassfish is unaware of any weld interceptors out there and therefore any calls to them must happen somewhere inside weld part of call stack, isn't it?

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