[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

[ https://issues.jboss.org/browse/CDI-223?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-223: ------------------------------- When you say "Imagine a @RequestScoped User CDI bean which gets injected into a @Stateless EJB. Your User will not be available for injection on the remote side! But this would perfectly work for a @Stateless bean which is local." Yes, you can't inject it using @Inject, but you still can via @EJB, in which case the CDI bean behaves as a "non-contextual instance". I was assuming @EJB injection for this clarification, sorry about that! Re @Timer, isn't that covered by "message-driven bean, >>>timeout<<< or..."? -- 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