[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

Fab Mars (JIRA) jira-events at lists.jboss.org
Mon Apr 30 09:50:18 EDT 2012


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

Fab Mars commented on CDI-223:
------------------------------

@Stateful + @EJB User may turn the use-case into something rigid/theoretical, don't you think?

Back to to the example, @Remote can't marry with CDI's jurisdiction boundaries. It's obvious and at the same time I feel there's going to be a lot of questions on user forums. It kind of reminds me of the lazy loading issue on detached JPA entities.

Well, so, logically (though it will require careful documenting), the only option is to pass a reference to the content you want to use within your EJB. Either you ask developpers to create an intermediate cdi-free "copy" of User(sounds oldschool to me), or take the road Mark outlined.

Unless there are so few Remote-EJB/CDI users that this issue is pointless, I think we have no choice.
                
> 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

        


More information about the cdi-dev mailing list