[
https://issues.jboss.org/browse/CDI-180?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-180:
-------------------------------
Decomposing this:
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.
Is the request context shared in this case?
The spec doesn't specify how the request context is shared. We should tidy this up.
Will be destroyed after the EJB remote method invocation?
I think this is fairly unambiguous given "The request context is destroyed: after the
EJB remote method invocation"!
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