4:18 p.m.
Guido Bonazza created CDI-219:
---------------------------------
Summary: 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
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:51 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Cody Lerum commented on CDI-219:
--------------------------------
This is a common issue for @Singleton + @Startup beans which have a @PostConstruct method
for initializing some application state at start-up.
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
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:13 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-219:
--------------------------
Fix Version/s: 1.1 (Proposed)
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
Fix For: 1.1 (Proposed)
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:15 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Pete Muir reassigned CDI-219:
-----------------------------
Assignee: Joe Bergmark
Assigning to Joe, as this is very closely related to CDI-235.
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 (Proposed)
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:15 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-219:
--------------------------
Fix Version/s: 1.1.PRD
(was: 1.1 (Proposed))
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:17 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Pete Muir resolved CDI-219.
---------------------------
Resolution: Done
Merged in Joe's fix. Thanks Joe!
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:08 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Guido Bonazza commented on CDI-219:
-----------------------------------
Sorry for being so late (and not having pointed out it immediatly), but... shouldn't
@PreDestroy callbacks deserve the same treatment?
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:16 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Guido Bonazza commented on CDI-219:
-----------------------------------
Also, I think it's important to specify that, for @Singleton EJBs, a new
RequestContext should always be created, regardless of whether one is already available,
otherwise the @Singleton behavior would not be predictable, being dependant on the first
request it is initialized for.
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:23 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Joe Bergmark commented on CDI-219:
----------------------------------
Two quick comments:
1) To me it doesn't make as much sense to do this for @PreDestroy. @PreqDestroy could
be getting called because the request context ended and we are cleaning up request scoped
beans. It seems strange to me that we would then create a new request context just for
that @PreDestroy invocation.
2) As Martin pointed out on my original pull request, that contradicts 6.3 that says we
can only have on per thread.
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
11:27 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-219:
-------------------------------
Singletons can only be @ApplicationScoped or @Dependent (see 3.2) so I'm not following
(1).
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
11:51 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Joe Bergmark commented on CDI-219:
----------------------------------
Sorry for not being very clean on my (1).
What I meant was the treatment we have @PostConstruct was for it to always be active
during @PostConstruct for basically any bean. We didn't specify @Singleton or @Remote
etc. If we did the same for @PreDestroy, we could end up in a situation where some
Request Context is ending, which causes @PreDestroy to be called for a request scoped
bean, and a new request context to be created which feels a bit strange to me.
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
12:25 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Guido Bonazza commented on CDI-219:
-----------------------------------
I actually don't have strong arguments for @PreDestroy, the main one is symmetry,
which is not completely fool since it's common to use the same resources in
@PreDestroy as in @PostConstruct.
Joe, I'm afraid I don't understand 2), (and I coudn't find Martin's
comment): my suggestion is that in @Singleton @PostConstruct (and eventually @PreDestroy)
the current RequestContext, if any, is "suspended" and "resumed" upon
exit of the callback. Does this contradict 6.3? This would be coherent with transactional
behaviour; otherwise we end up with a new transaction opened on the @Singleton
@PostConstruct invocation, suspending the current one, all within the same RequestContext
which could lead to weird side effects I think.
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
5:22 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-219:
-------------------------------
Yes, this contradicts the defined threading semantics of CDI 1.0. Contexts must always be
joined if they are alive.
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
11:46 a.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Guido Bonazza commented on CDI-219:
-----------------------------------
Doesn't the TransactionContext (see CDI-121) already violate this principle? I suppose
that, if a transaction is suspended and a new one is begun, the corresponding context is
suspended as well and a new one is created/activated. I'm just guessing here about
TransactionContext so maybe I'm wrong, but it seems to me that the threading semantics
of CDI 1.0 is a bit limiting.
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
2:59 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-219:
-------------------------------
I don't see a conflict here. The current transaction context is suspended, and a new
one is created. There aren't two alive at the same point in time on the same thread.
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
3:32 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
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
3:44 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-219:
-------------------------------
Yes, I was being lazy in my language ;-) (b) is correct.
And the issue is the implication of CDI 1.0 6.3 and lack of definition of such a
suspension as you propose in 1.0. Any such change would not be backwards compatible at
all.
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
2:15 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Jozef Hartinger reopened CDI-219:
---------------------------------
I just realized that we have to add the special case of activating @RequestScope for a
@PostConstruct invocation to the last part of section 6.7.1 that lists the payload of
@Initialized and @Destroyed requests. The case of @PostConstruct callback is currently
missing.
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
2:24 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-219:
--------------------------
Fix Version/s: 1.1 (Proposed)
(was: 1.1.PRD)
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: Pete Muir
Fix For: 1.1 (Proposed)
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
2:24 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Pete Muir reassigned CDI-219:
-----------------------------
Assignee: Pete Muir (was: Joe Bergmark)
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: Pete Muir
Fix For: 1.1 (Proposed)
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
5:21 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Pete Muir resolved CDI-219.
---------------------------
Fix Version/s: 1.1.PRD
(was: 1.1 (Proposed))
Resolution: Done
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: Pete Muir
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
5:21 p.m.
[
https://issues.jboss.org/browse/CDI-219?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-219:
-------------------------------
This was addressed as part of the CDI-207 commit.
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: Pete Muir
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
4241
days inactive
4432
days old
21 comments
5 participants
participants (5)
-
Cody Lerum (JIRA) -
Guido Bonazza (JIRA)
-
Joe Bergmark (JIRA)
-
Jozef Hartinger (JIRA)
-
Pete Muir (JIRA)