[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

[Norman Richards (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-3095?page=comments#action_12416910 ] 
            
Norman Richards commented on JBSEAM-3095:
-----------------------------------------

Ok, this just won't work with session beans due to the inherent flaws of session beans around reentrant calls.  I'm tempted to suggest making the proposed change anyway and simply live with the limitations of session beans, but that would actually break code that already "works" now.  

I think the simplest solution here is to use an asynchronous event if you are calling back to yourself and need Seam to be involved with the call.  That's not ideal, but I think it's the best we can do given the circumstances.


> 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