[cdi-dev] [JBoss JIRA] (CDI-180) Clarify request context lifecycle during remote method invocation of EJB

[Stuart Douglas (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/CDI-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637512#comment-12637512 ] 

Stuart Douglas commented on CDI-180:
------------------------------------

>> However it doesn't cover various invocation scenarios. For example it's
>> possible to do in-VM invocation (via remote interface) from the same
>> deployment or from a different deployment.
>
>I don't see why the spec implies this is treated any differently.

I think the real question here is that if you have 2 CDI applications, and they communicate via in-vm method calls, does the bean in the second application live for a single invocation, or does it last for the life of the calling request scope. I would assume the former.




 
                
> Clarify request context lifecycle during remote method invocation of EJB
> ------------------------------------------------------------------------
>
>                 Key: CDI-180
>                 URL: https://issues.jboss.org/browse/CDI-180
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>    Affects Versions: 1.0
>            Reporter: Martin Kouba
>
> CDI 1.0 spec states in *6.7.1. Request context lifecycle*:
> "The request scope is active: during any remote method invocation of any EJB" and "The request context is destroyed: after the EJB remote method invocation"
> However it doesn't cover various invocation scenarios. For example it's possible to do in-VM invocation (via remote interface) from the same deployment or from a different deployment. Is the request context shared in this case? Will be destroyed after the EJB remote method invocation?
> Also take into account that application servers often do optimization and handle remote interface calls in a local interface manner within the same JVM.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira