January 2017 - cdi-dev - Jboss List Archives

InvocationScoped | RequestScoped thread context

by Sebastian Daschner

Hi experts, Regarding scopes, specificly @RequestScoped: We found in enterprise projects that there is a need for a request / invocation scope that is active during an invocation of a business method (HTTP, JMS, EJB, timer, whatever), regardless how many threads are involved. Naively, one could presume that @RequestScoped would deal that, but since it's strictly single threaded and not accessible from asyncronously started threads (ManagedExecuterService and so forth) that doesn't help much. This scope would e.g. enable correlation IDs that are needed in all threads started from one original invocation. Name is up to better suggestions :-) I guess it's not possible to change the behavior of @RequestScoped and to make it available in asyncronously started threads? Have there been considerations for adding such a scope or similar in the past? Cheers, Sebastian

7 years, 11 months

3
2
0 / 0

[JBoss JIRA] (CDI-678) Consider expanding @WithAnnotations utilization

by Tomas Remes (JIRA)

Tomas Remes created CDI-678: ------------------------------- Summary: Consider expanding @WithAnnotations utilization Key: CDI-678 URL: https://issues.jboss.org/browse/CDI-678 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Tomas Remes Priority: Minor Currently usage of {{@WithAnnotations}} is available only with {{ProcessAnnotatedType}} event. Maybe it could be helpful to expand this option also for other lifecycle events. For example I came across this extension https://github.com/wildfly-swarm/wildfly-swarm/blob/master/core/container... It basically observes all {{ProcessInjectionTarget}} events and tries to find {{@Configurable}} annotation in the related {{AnnotatedType}} (which is available in this case). Allowing to use {{@WithAnnotations}} in this case would solve this problem more gracefully I believe. It's likely minor enhancement but maybe it could be useful also in another cases. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (CDI-678) Consider expanding @WithAnnotations utilization

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-678?page=com.atlassian.jira.plugin.sy... ] Tomas Remes updated CDI-678: ---------------------------- Fix Version/s: 2.1 (Discussion) > Consider expanding @WithAnnotations utilization > ----------------------------------------------- > > Key: CDI-678 > URL: https://issues.jboss.org/browse/CDI-678 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Tomas Remes > Priority: Minor > Fix For: 2.1 (Discussion) > > > Currently usage of {{@WithAnnotations}} is available only with {{ProcessAnnotatedType}} event. Maybe it could be helpful to expand this option also for other lifecycle events. > For example I came across this extension https://github.com/wildfly-swarm/wildfly-swarm/blob/master/core/container... > It basically observes all {{ProcessInjectionTarget}} events and tries to find {{@Configurable}} annotation in the related {{AnnotatedType}} (which is available in this case). Allowing to use {{@WithAnnotations}} in this case would solve this problem more gracefully I believe. > It's likely minor enhancement but maybe it could be useful also in another cases. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (CDI-644) Link formatting in the specification text

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-644?page=com.atlassian.jira.plugin.sy... ] Tomas Remes commented on CDI-644: --------------------------------- Ok it seems HTML is the same. I thought PDF - http://docs.jboss.org/cdi/spec/1.2/cdi-spec-1.2.pdf > Link formatting in the specification text > ------------------------------------------ > > Key: CDI-644 > URL: https://issues.jboss.org/browse/CDI-644 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Tomas Remes > Fix For: 2.0 .Final > > > In previous versions (1.x) of specification links to chapters within spec were formatted as follows: > {noformat} > Section 2.4.1, “Built-in scope types” > {noformat} > I would like to preserve this formatting (especialy the prefix "Section x.x.x") also in the new specification version because I think it's more legible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (CDI-644) Link formatting in the specification text

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-644?page=com.atlassian.jira.plugin.sy... ] Tomas Remes updated CDI-644: ---------------------------- Description: In previous versions (1.x) of specification links to chapters within spec were formatted as follows: {noformat} Section 2.4.1, “Built-in scope types” {noformat} I would like to preserve this formatting (especialy the prefix "Section x.x.x") also in the new specification version because I think it's more legible. was: In the last version of specification there was good use of link formatting in the text. It looks as follows: {noformat} Section 2.4.1, “Built-in scope types” {noformat} I would like to keep this format (especialy the prefix "Section x.x.x") also in the new version because I think it's more legible. > Link formatting in the specification text > ------------------------------------------ > > Key: CDI-644 > URL: https://issues.jboss.org/browse/CDI-644 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Tomas Remes > Fix For: 2.0 .Final > > > In previous versions (1.x) of specification links to chapters within spec were formatted as follows: > {noformat} > Section 2.4.1, “Built-in scope types” > {noformat} > I would like to preserve this formatting (especialy the prefix "Section x.x.x") also in the new specification version because I think it's more legible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

Thread safety of SeContainer and SeContainerInitializer

by Laird Nelson

Are SeContainer and SeContainerInitializer safe for concurrent use by multiple threads? The string "concurren" shows up only four times in the 2.0 specification but not in this context. I'm most interested in whether it is guaranteed that one thread may call SeContainer::initialize and another may call SeContainer::close. I'm assuming that this is *not* guaranteed. Best, Laird

7 years, 11 months

3
5
0 / 0

[JBoss JIRA] (CDI-644) Link formatting in the specification text

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-644?page=com.atlassian.jira.plugin.sy... ] Tomas Remes updated CDI-644: ---------------------------- Fix Version/s: 2.0 .Final What about this one? Personally I would like to see it in 2.0.Final but it's likely minor. > Link formatting in the specification text > ------------------------------------------ > > Key: CDI-644 > URL: https://issues.jboss.org/browse/CDI-644 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Tomas Remes > Fix For: 2.0 .Final > > > In the last version of specification there was good use of link formatting in the text. It looks as follows: > {noformat} > Section 2.4.1, “Built-in scope types” > {noformat} > I would like to keep this format (especialy the prefix "Section x.x.x") also in the new version because I think it's more legible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (CDI-672) Purpose of BeanAttributesConfigurator read methods

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/CDI-672?page=com.atlassian.jira.plugin.sy... ] Matej Novotny reassigned CDI-672: --------------------------------- Assignee: Matej Novotny (was: Antoine Sabot-Durand) > Purpose of BeanAttributesConfigurator read methods > --------------------------------------------------- > > Key: CDI-672 > URL: https://issues.jboss.org/browse/CDI-672 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 2.0.Beta1 > Reporter: Tomas Remes > Assignee: Matej Novotny > Fix For: 2.0 .Final > > > I think we already discussed and agreed to remove these read methods from {{BeanAttributesConfigurator}}. I can't remember the arguments for this but I think I simply forgot to mention it in https://issues.jboss.org/browse/CDI-614 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (CDI-672) Purpose of BeanAttributesConfigurator read methods

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/CDI-672?page=com.atlassian.jira.plugin.sy... ] Matej Novotny updated CDI-672: ------------------------------ Git Pull Request: https://github.com/cdi-spec/cdi/pull/369 > Purpose of BeanAttributesConfigurator read methods > --------------------------------------------------- > > Key: CDI-672 > URL: https://issues.jboss.org/browse/CDI-672 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 2.0.Beta1 > Reporter: Tomas Remes > Assignee: Matej Novotny > Fix For: 2.0 .Final > > > I think we already discussed and agreed to remove these read methods from {{BeanAttributesConfigurator}}. I can't remember the arguments for this but I think I simply forgot to mention it in https://issues.jboss.org/browse/CDI-614 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (CDI-668) Most Example with @Priority provide non fully qualified contant name

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-668?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand reassigned CDI-668: ---------------------------------------- Assignee: Antoine Sabot-Durand > Most Example with @Priority provide non fully qualified contant name > -------------------------------------------------------------------- > > Key: CDI-668 > URL: https://issues.jboss.org/browse/CDI-668 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 2.0.Beta1 > Reporter: Antoine Sabot-Durand > Assignee: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > Example in spec show {{@Priority}} are assuming static import of {{javax.interceptor.Interceptor.Priority.APPLICATION}} > We should change them to show full qualified path or add static import to examples for readability sake. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev January 2017