April 2014 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-431) BeanManager Javadoc inconsistency

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-431: ----------------------------------- Summary: BeanManager Javadoc inconsistency Key: CDI-431 URL: https://issues.jboss.org/browse/CDI-431 Project: CDI Specification Issues Issue Type: Bug Components: Portable Extensions Reporter: Jozef Hartinger Assignee: Antoine Sabot-Durand Fix For: 1.2 Proposed https://github.com/cdi-spec/cdi/blob/master/api/src/main/java/javax/enter... vs https://github.com/cdi-spec/cdi/blob/master/api/src/main/java/javax/enter... -- 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

10 years

1
0
0 / 0

Last review on CDI-430 PR

by Antoine Sabot-Durand

Hi all, I integrated Pete comments and switch filtering and type discovery parts. Please review these small last changes ASAP [1]. [1] https://github.com/cdi-spec/cdi/pull/233 Thanks Antoine

10 years

1
0
0 / 0

[JBoss JIRA] (CDI-430) Revise the description of container lifecycle ordering during application initialization

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-430?page=com.atlassian.jira.plugin.sy... ] Work on CDI-430 started by Antoine Sabot-Durand. > Revise the description of container lifecycle ordering during application initialization > ---------------------------------------------------------------------------------------- > > Key: CDI-430 > URL: https://issues.jboss.org/browse/CDI-430 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.1.Final > Reporter: Martin Kouba > Assignee: Antoine Sabot-Durand > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > E.g. it's not entirely clear when {{ProcessInjectionPoint}} if fired. Also it would be useful to mention {{ProcessBeanAttributes}} in bean discovery section. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (CDI-430) Revise the description of container lifecycle ordering during application initialization

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-430?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger reopened CDI-430: --------------------------------- Sorry for late review. There are several problems with the change: 1) Determining enabled alternatives, interceptors and decorators 12.4.3 has two bullets starting with: "if the class is an enabled bean, interceptor or decorator, create ..." and then the spec says: "Then, the container determines which alternatives, interceptors and decorators are enabled ..." The ordering here is clearly wrong (here since enabled beans, interceptors and decorators need to actually be determined for ProcessBean / ProcessBeanAttributes) 2) Strict ordering The current ordering rules are way too strict. For example, the following ordering is required: - create InjectionTarget, then - fire ProcessInjectionTarget, and later - create a Bean object However, this cannot be implemented since an observer for ProcessInjectionTarget may call: ProcessInjectionTarget.getInjectionTarget().getInjectionPoints().getBean() Since the Bean object has not been created yet the container cannot fulfil the contract. Same for ProcessInjectionPoint. 3) ProcessInjectionPoint should also be fired for InjectionPoints of producers/observers. The CDI 1.1 wording does not make that explicit. The current CDI-430 solution does not reflect this either within the new event ordering. > Revise the description of container lifecycle ordering during application initialization > ---------------------------------------------------------------------------------------- > > Key: CDI-430 > URL: https://issues.jboss.org/browse/CDI-430 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.1.Final > Reporter: Martin Kouba > Assignee: Antoine Sabot-Durand > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > E.g. it's not entirely clear when {{ProcessInjectionPoint}} if fired. Also it would be useful to mention {{ProcessBeanAttributes}} in bean discovery section. -- 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

10 years

1
0
0 / 0

Please review new PR for CDI-392

by Antoine Sabot-Durand

Hi all, Just posted new Pull Request for our final ticket. Please take time to review it ASAP, so we could close the MR tonight. https://github.com/cdi-spec/cdi/pull/232 Thanks a lot. Antoine

10 years

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 reassigned CDI-392: ---------------------------------------- Assignee: Antoine Sabot-Durand (was: Mark Struberg) > 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: Antoine Sabot-Durand > 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

10 years

1
0
0 / 0

[JBoss JIRA] (CDI-385) ProcessObserverMethod is different btw spec and API

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-385?page=com.atlassian.jira.plugin.sy... ] Work on CDI-385 started by Antoine Sabot-Durand. > ProcessObserverMethod is different btw spec and API > --------------------------------------------------- > > Key: CDI-385 > URL: https://issues.jboss.org/browse/CDI-385 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API > Affects Versions: 1.1.PFD > Reporter: Mark Struberg > Assignee: Antoine Sabot-Durand > Priority: Critical > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > As stated in CDI-88 the spec and API is different for ProcessObserverMethod. > In the spec there is a method > public AnnotatedParameter<T> getAnnotatedEventParameter(); > but in the API there is > AnnotatedMethod<X> getAnnotatedMethod(); > which imo makes much more sense anyway. > Thus we should amend the spec wording finally. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (CDI-385) ProcessObserverMethod is different btw spec and API

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-385?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-385: ------------------------------------- Labels: CDI_spec_chge Ready_to_fix (was: ) > ProcessObserverMethod is different btw spec and API > --------------------------------------------------- > > Key: CDI-385 > URL: https://issues.jboss.org/browse/CDI-385 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API > Affects Versions: 1.1.PFD > Reporter: Mark Struberg > Priority: Critical > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > As stated in CDI-88 the spec and API is different for ProcessObserverMethod. > In the spec there is a method > public AnnotatedParameter<T> getAnnotatedEventParameter(); > but in the API there is > AnnotatedMethod<X> getAnnotatedMethod(); > which imo makes much more sense anyway. > Thus we should amend the spec wording finally. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (CDI-385) ProcessObserverMethod is different btw spec and API

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-385?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand reassigned CDI-385: ---------------------------------------- Assignee: Antoine Sabot-Durand > ProcessObserverMethod is different btw spec and API > --------------------------------------------------- > > Key: CDI-385 > URL: https://issues.jboss.org/browse/CDI-385 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API > Affects Versions: 1.1.PFD > Reporter: Mark Struberg > Assignee: Antoine Sabot-Durand > Priority: Critical > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > As stated in CDI-88 the spec and API is different for ProcessObserverMethod. > In the spec there is a method > public AnnotatedParameter<T> getAnnotatedEventParameter(); > but in the API there is > AnnotatedMethod<X> getAnnotatedMethod(); > which imo makes much more sense anyway. > Thus we should amend the spec wording finally. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (CDI-385) ProcessObserverMethod is different btw spec and API

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-385?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-385: ------------------------------------- Fix Version/s: 1.2 Proposed > ProcessObserverMethod is different btw spec and API > --------------------------------------------------- > > Key: CDI-385 > URL: https://issues.jboss.org/browse/CDI-385 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API > Affects Versions: 1.1.PFD > Reporter: Mark Struberg > Priority: Critical > Fix For: 1.2 Proposed > > > As stated in CDI-88 the spec and API is different for ProcessObserverMethod. > In the spec there is a method > public AnnotatedParameter<T> getAnnotatedEventParameter(); > but in the API there is > AnnotatedMethod<X> getAnnotatedMethod(); > which imo makes much more sense anyway. > Thus we should amend the spec wording finally. -- 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

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev April 2014