[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3095) observing events in the same component the raised one results in interceptors not being run on the observer message
[ http://jira.jboss.com/jira/browse/JBSEAM-3095?page=comments#action_12416598 ]
Dan Allen commented on JBSEAM-3095:
-----------------------------------
It would help if someone could explain exactly why the non-proxied object is needed in the
method context. I'm not saying there isn't a reason, it would just help if we
could get a use case that explains the motivation.
observing events in the same component the raised one results in
interceptors not being run on the observer message
-------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3095
URL: http://jira.jboss.com/jira/browse/JBSEAM-3095
Project: Seam
Issue Type: Bug
Reporter: Norman Richards
Assigned To: Norman Richards
Fix For: 2.1.0.BETA1, 2.0.3.GA
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira