[cdi-dev] [JBoss JIRA] (CDI-223) Verify that it's 100% clear that any EJB "remote" invocation which doesn't occur when an existing request context is active, starts/ends it's own request context

Mon Apr 30 12:53:17 EDT 2012

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

Mark Struberg commented on CDI-223:
-----------------------------------

Maybe we should handle this the same way we need to handle @Asynchronous? To add the explicit boundary saying what parts and mechanisms get their own RequestContext. Or just saying that any CDI Context doesn't get propagated to EJB remote instances.

Even if the desired behaviour seems obvious - it is unspecified as long as we don't explicitly define it.

> Verify that it's 100% clear that any EJB "remote" invocation which doesn't occur when an existing request context is active, starts/ends it's own request context
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CDI-223
>                 URL: https://issues.jboss.org/browse/CDI-223
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>            Reporter: Pete Muir
>
> This should apply to JVM-local or JVM-remote remote invocations

--
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