[
https://issues.jboss.org/browse/CDI-732?page=com.atlassian.jira.plugin.sy...
]
Matej Novotny commented on CDI-732:
-----------------------------------
bq. conversation is clearly longer than request. Thus this argument makes no sense.
Clearly not so much when it is transient, so it makes sense. The lifespan of a
conversation can differ and there is no "perfect fit" for it.
Clarify that the Context for RequestScoped must be active during
@PreDestroy calls
----------------------------------------------------------------------------------
Key: CDI-732
URL:
https://issues.jboss.org/browse/CDI-732
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 2.0 .Final
Reporter: Mark Struberg
We have the explicit rule that the Context for @RequestScoped must be active during
@PostConstruct of any bean.
But it seems we don't force the same for invocations of @PreDestroy methods.
That's especially weird since a few containers now blow up during a destroyal of a
@SessionScopedBean which has a @RequestScoped Principal injected, even if the session
destroyal was triggered by an explicit Session#invalidate() call in an open HTTP request.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)