March 2014 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-429) Consistency of all built-in normal scopes

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-429?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-429: ------------------------------------- Labels: CDI_api_chge CDI_spec_chge reasd (was: CDI_api_chge CDI_spec_chge) > Consistency of all built-in normal scopes > ----------------------------------------- > > Key: CDI-429 > URL: https://issues.jboss.org/browse/CDI-429 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Contexts > Affects Versions: 1.1.Final > Reporter: Antoine Sabot-Durand > Assignee: Antoine Sabot-Durand > Labels: CDI_api_chge, CDI_spec_chge, reasd > Fix For: 1.2 Proposed > > > In CDI-381, we added comment to indicate that third party can use @Requestscoped to bind their own context. > For consistency we should do the same for all Normal Scopes. And also check spec as well. -- 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

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-429) Consistency of all built-in normal scopes

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-429?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand reassigned CDI-429: ---------------------------------------- Assignee: Antoine Sabot-Durand > Consistency of all built-in normal scopes > ----------------------------------------- > > Key: CDI-429 > URL: https://issues.jboss.org/browse/CDI-429 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Contexts > Affects Versions: 1.1.Final > Reporter: Antoine Sabot-Durand > Assignee: Antoine Sabot-Durand > Labels: CDI_api_chge, CDI_spec_chge > Fix For: 1.2 Proposed > > > In CDI-381, we added comment to indicate that third party can use @Requestscoped to bind their own context. > For consistency we should do the same for all Normal Scopes. And also check spec as well. -- 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

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-380) Clarify SessionScoped

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-380?page=com.atlassian.jira.plugin.sy... ] Work on CDI-380 started by Antoine Sabot-Durand. > Clarify SessionScoped > --------------------- > > Key: CDI-380 > URL: https://issues.jboss.org/browse/CDI-380 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Joseph Snyder > Assignee: Antoine Sabot-Durand > Priority: Minor > Labels: CDI_api_chge, CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > The javadocs say: > The request context is destroyed: > - at the end of the servlet request, after the service() method, all > doFilter() methods, and all requestDestroyed() and onComplete() > notifications return, > ... > The session context is destroyed when the HTTPSession times out, after all > HttpSessionListeners have been called, and at the very end of any request in > which invalidate() was called, after all filters and ServletRequestListeners > have been called. > Those definitions are different. > The session context rule seems to be a combination of "or" items that > include some "and" items. It's difficult to parse. It would be clearer > if it was written as a list. And, like request scoped, it would be clearer > if it described when the session scope/context is created. -- 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

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-392) Clarify when the operations of BeanManager can be called

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-392?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-392: ------------------------------------------ +1 > Clarify when the operations of BeanManager can be called > -------------------------------------------------------- > > Key: CDI-392 > URL: https://issues.jboss.org/browse/CDI-392 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Matus Abaffy > Assignee: Mark Struberg > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > The current version of spec. states (under 11.3. The BeanManager object): "Any operation of BeanManager may be called at any time during the execution of the application." > This sentence is likely to be misinterpreted (see WELD-1453). Pointing out that BeanManager's methods can be called (without causing exception) just after AfterDeploymentValidation event is fired might be helpful. -- 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

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-392) Clarify when the operations of BeanManager can be called

by Mark Struberg (JIRA)

[ https://issues.jboss.org/browse/CDI-392?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-392: ----------------------------------- As we agree that those sentences make no sense: should we remove those? > Clarify when the operations of BeanManager can be called > -------------------------------------------------------- > > Key: CDI-392 > URL: https://issues.jboss.org/browse/CDI-392 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Matus Abaffy > Assignee: Mark Struberg > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > The current version of spec. states (under 11.3. The BeanManager object): "Any operation of BeanManager may be called at any time during the execution of the application." > This sentence is likely to be misinterpreted (see WELD-1453). Pointing out that BeanManager's methods can be called (without causing exception) just after AfterDeploymentValidation event is fired might be helpful. -- 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

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-429) Consistency of all built-in normal scopes

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-429?page=com.atlassian.jira.plugin.sy... ] Martin Kouba updated CDI-429: ----------------------------- Summary: Consistency of all built-in normal scopes (was: Consistency of all Normal Scopes) > Consistency of all built-in normal scopes > ----------------------------------------- > > Key: CDI-429 > URL: https://issues.jboss.org/browse/CDI-429 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Contexts > Affects Versions: 1.1.Final > Reporter: Antoine Sabot-Durand > Labels: CDI_api_chge, CDI_spec_chge > Fix For: 1.2 Proposed > > > In CDI-381, we added comment to indicate that third party can use @Requestscoped to bind their own context. > For consistency we should do the same for all Normal Scopes. And also check spec as well. -- 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

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-429) Consistency of all Normal Scopes

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-429?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-429: ------------------------------------- Summary: Consistency of all Normal Scopes (was: Consistency of all Noraml Scopes) > Consistency of all Normal Scopes > -------------------------------- > > Key: CDI-429 > URL: https://issues.jboss.org/browse/CDI-429 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Contexts > Affects Versions: 1.1.Final > Reporter: Antoine Sabot-Durand > Labels: CDI_api_chge, CDI_spec_chge > Fix For: 1.2 Proposed > > > In CDI-381, we added comment to indicate that third party can use @Requestscoped to bind their own context. > For consistency we should do the same for all Normal Scopes. And also check spec as well. -- 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

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-429) Consistency of all Noraml Scopes

by Antoine Sabot-Durand (JIRA)

Antoine Sabot-Durand created CDI-429: ---------------------------------------- Summary: Consistency of all Noraml Scopes Key: CDI-429 URL: https://issues.jboss.org/browse/CDI-429 Project: CDI Specification Issues Issue Type: Clarification Components: Contexts Affects Versions: 1.1.Final Reporter: Antoine Sabot-Durand Fix For: 1.2 Proposed In CDI-381, we added comment to indicate that third party can use @Requestscoped to bind their own context. For consistency we should do the same for all Normal Scopes. And also check spec as well. -- 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

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-320) Clarify whether ProcessAnnotatedType should be fired for annotations

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-320?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-320: ------------------------------------------ Seriously [~jharting]? I must admit I found this sentence not very clear... Thanks both for that discovery. I remove it from the PR. > Clarify whether ProcessAnnotatedType should be fired for annotations > -------------------------------------------------------------------- > > Key: CDI-320 > URL: https://issues.jboss.org/browse/CDI-320 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Portable Extensions > Reporter: Ron Šmeral > Assignee: Antoine Sabot-Durand > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > It should be stated clearly whether {{ProcessAnnotatedType}} should be fired for annotations. > Currently, *11.5.6 ProcessAnnotatedType event* says: > {quote} > The container must fire an event, before it processes a type, for each: > * Java class, interface or enum in a bean archive, > {quote} > The word "annotation" has been introduced into the above line and later reverted. > {quote} > * Annotated type added by {{BeforeBeanDiscovery.addAnnotatedType()}}, > {quote} > The wording used here, however, doesn't exclude the option of the annotated type being an Annotation. -- 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

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-320) Clarify whether ProcessAnnotatedType should be fired for annotations

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-320?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger commented on CDI-320: ------------------------------------- {quote}the third point, which deals with @WithAnnotations doesn't seem to belong to the paragraph, as the paragraph talks about what the container must fire, not about what the observers must handle. The point seems redundant because the set of every Java class, interface or enum discovered fully includes the set of annotated Java classes, interfaces or enums discovered.{quote} I think you are referring to this part: {quote}each Java class, interface or enum that must be delivered to a ProcessAnnotatedType observer, where the event parameter is annotated with @WithAnnotations.{quote} This is indeed a leftover from pre-final version of CDI 1.1. This feature did not make it into the final version. We should remove this leftover. > Clarify whether ProcessAnnotatedType should be fired for annotations > -------------------------------------------------------------------- > > Key: CDI-320 > URL: https://issues.jboss.org/browse/CDI-320 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Portable Extensions > Reporter: Ron Šmeral > Assignee: Antoine Sabot-Durand > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > It should be stated clearly whether {{ProcessAnnotatedType}} should be fired for annotations. > Currently, *11.5.6 ProcessAnnotatedType event* says: > {quote} > The container must fire an event, before it processes a type, for each: > * Java class, interface or enum in a bean archive, > {quote} > The word "annotation" has been introduced into the above line and later reverted. > {quote} > * Annotated type added by {{BeforeBeanDiscovery.addAnnotatedType()}}, > {quote} > The wording used here, however, doesn't exclude the option of the annotated type being an Annotation. -- 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

9 years, 2 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev March 2014