[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
Mark Struberg (JIRA)
jira-events at lists.jboss.org
Mon Apr 30 06:35:17 EDT 2012
[ https://issues.jboss.org/browse/CDI-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688743#comment-12688743 ]
Mark Struberg commented on CDI-223:
-----------------------------------
I meant the EJB-2.1 Timer interface. @Timeout etc, but also programmatically managed TimedObjects ...
> 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