|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
Yeah, you may be right, but when it comes to EJBs, it's not always Weld that does all the work. I wasn't sure if glassfish-weld integration gets invoked or not when the observer method's declaring bean is an EJB.
I ran the test against GlassFish 3.1.2.2 and the test passes. I've also added System.out calls to both the observer and interceptor and can see them in the log.
So I'm not sure, why it doesn't work for you. Do you have the beans.xml in the right place? Have you tried adding the same interceptor binding to any other (non-observer) method and testing if the interceptor fires?