[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

[Pete Muir (JIRA)]

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

Pete Muir commented on CDI-223:
-------------------------------

Yes, you would need to make this as a *class* bean, which can be an EJB as well. e.g.

{code}
@Stateful
@RequestScoped
public class User {

   ...

   private String getId() { ... }

}
{code}

{code}
@Stateful
public class RemoteBean {

   @EJB User user;

   public void doSomething() {
      String id = user.getId();
   }

}
{code}

Is what would work.

If you want to make user produced, you'll need some sort delegate or something, which is a really mess.
                
> 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