[
https://jira.jboss.org/jira/browse/JBSEAM-3095?page=com.atlassian.jira.pl...
]
Chris Simons commented on JBSEAM-3095:
--------------------------------------
Seam Team,
In your opinion, could the custom interceptor solution described in the reference above
impact compatibility with current and/or future releases of Seam? Is it currently the
recommended solution for this problem?
Thanks.
observing events in the same component the raised one results in
interceptors not being run on the observer message
-------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3095
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3095
Project: Seam
Issue Type: Bug
Reporter: Norman Richards
Assignee: Norman Richards
Fix For: The future
This is due to the MethodContextInterceptor imposing the unproxied object on the user. I
think the fix is to make sure that events happen in a distinct method context. I've
tested this with javabean components, but session beans might be trickier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira