[cdi-dev] [JBoss JIRA] (CDI-219) Support Request Scope for EJB @Singleton @PostConstruct methods

Guido Bonazza (JIRA) jira-events at lists.jboss.org
Fri Aug 31 09:32:32 EDT 2012

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

Guido Bonazza commented on CDI-219:

Saying (a) "Contexts must always be joined if they are alive" and (b) "There aren't two alive at the same point in time on the same thread" are different things, right?
My proposal for @Singleton @PostConstruct (and @PreDestroy) is that the RequestContext should behave exactly like the TransactionContext, that is, to suspend the current context and activate a new one; this does violate (a) but not (b), just like TransactionContext.
Reading 6.3, it seems to me that (b) is clearly implied, but I cannot find (a), both in CDI 1.0 and in the current draft of 1.1. Am I missing something?
> Support Request Scope for EJB @Singleton @PostConstruct methods
> ---------------------------------------------------------------
>                 Key: CDI-219
>                 URL: https://issues.jboss.org/browse/CDI-219
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Contexts, Java EE integration
>    Affects Versions: 1.0
>            Reporter: Guido Bonazza
>            Assignee: Joe Bergmark
>             Fix For: 1.1.PRD
> A Request context should be available in @PostConstruct methods of EJB Singletons.
> This is a completion of section 6.7.1 of the CDI 1.0 spec, which covers @Asynchronous and @Timeout EJB methods.
> Probably the container should ensure that a new context is always created for the @PostConstruct invocation, to be coherent with section 4.8.3 of the EJB 3.1 spec, which specifies the transactional behavior of @Singleton @PostConstruct.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the cdi-dev mailing list