[JBoss JIRA] (CDI-635) Session context activation
by John Ament (JIRA)
John Ament created CDI-635:
------------------------------
Summary: Session context activation
Key: CDI-635
URL: https://issues.jboss.org/browse/CDI-635
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.2.Final
Reporter: John Ament
This is split from discussions around CDI-30. It was agreed that session context management and request context management are two different things. CDI-30 is now targeted to just managing request contexts, this ticket is to manage session contexts.
When considering this ticket, think of the following:
- How to associate a context with multiple threads
- How to look up a session context
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (CDI-634) Clarify contextual reference validity to a bean with a normal scope in Java SE
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/CDI-634?page=com.atlassian.jira.plugin.sy... ]
Matej Novotny edited comment on CDI-634 at 10/3/16 6:42 AM:
------------------------------------------------------------
+1 for clarification
Although it is 'deducible' for us, it won't hurt to mention it as it indeed can be tempting.
EDIT: drafted a PR for this - https://github.com/cdi-spec/cdi/pull/304
was (Author: manovotn):
+1 for clarification
Although it is 'deducible' for us, it won't hurt to mention it as it indeed can be tempting.
> Clarify contextual reference validity to a bean with a normal scope in Java SE
> ------------------------------------------------------------------------------
>
> Key: CDI-634
> URL: https://issues.jboss.org/browse/CDI-634
> Project: CDI Specification Issues
> Issue Type: Clarification
> Reporter: Martin Kouba
>
> In Java SE, a user might be tempted to share a contextual reference for a normal scoped bean (client proxy) between multiple "deployments" of a single application, e.g.:
> # start CDI container
> # get a reference
> # stop CDI container
> # start CDI container again and try to use the stored reference.
> I believe such a reference should not be valid after an application stopped (contexts are destroyed, etc.). Right now, it seems to be undefined.
> See also WELD-2190.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (CDI-634) Clarify contextual reference validity to a bean with a normal scope in Java SE
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/CDI-634?page=com.atlassian.jira.plugin.sy... ]
Matej Novotny commented on CDI-634:
-----------------------------------
+1 for clarification
Although it is 'deducible' for us, it won't hurt to mention it as it indeed can be tempting.
> Clarify contextual reference validity to a bean with a normal scope in Java SE
> ------------------------------------------------------------------------------
>
> Key: CDI-634
> URL: https://issues.jboss.org/browse/CDI-634
> Project: CDI Specification Issues
> Issue Type: Clarification
> Reporter: Martin Kouba
>
> In Java SE, a user might be tempted to share a contextual reference for a normal scoped bean (client proxy) between multiple "deployments" of a single application, e.g.:
> # start CDI container
> # get a reference
> # stop CDI container
> # start CDI container again and try to use the stored reference.
> I believe such a reference should not be valid after an application stopped (contexts are destroyed, etc.). Right now, it seems to be undefined.
> See also WELD-2190.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months