April 2014 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-434) AfterTypeDiscovery javadoc outdated

by Martin Kouba (JIRA)

Martin Kouba created CDI-434: -------------------------------- Summary: AfterTypeDiscovery javadoc outdated Key: CDI-434 URL: https://issues.jboss.org/browse/CDI-434 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 1.2.Final Reporter: Martin Kouba {quote} *getAlternatives()* returns the ordered list of enabled alternatives for the application. Alternatives enabled for a bean archive are not included in the list {quote} vs http://docs.jboss.org/cdi/api/1.2/javax/enterprise/inject/spi/AfterTypeDi... The same applies to {{getInterceptors()}} and {{getDecorators()}}. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-433) AdminEvent example has redundant qualifiers.

by John Ament (JIRA)

[ https://issues.jboss.org/browse/CDI-433?page=com.atlassian.jira.plugin.sy... ] John Ament updated CDI-433: --------------------------- Affects Version/s: 1.2.Final > AdminEvent example has redundant qualifiers. > -------------------------------------------- > > Key: CDI-433 > URL: https://issues.jboss.org/browse/CDI-433 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.2.Final > Reporter: John Ament > Priority: Minor > > In the CDI 1.2 spec, the following text appears: > For example, this injected Event has specified type LoggedInEvent and specified qualifier @Admin: > {{@Inject @Admin Event<LoggedInEvent> any;}} > The select() method returns a child Event for a given specified type and additional specified qualifiers. If no specified type is given, the specified type is the same as the parent. > For example, this child Event has required type AdminLoggedInEvent and additional specified qualifier {{@Admin}}: > {noformat} > Event<AdminLoggedInEvent> admin = any.select( > AdminLoggedInEvent.class, > new AdminQualifier() ); > {noformat} > The problem is that the injection point any already is qualified @Admin, so the use is duplicate here. I believe the intention was that the injection point would read > {{@Inject Event<LoggedInEvent> any;}} -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-433) AdminEvent example has redundant qualifiers.

by John Ament (JIRA)

John Ament created CDI-433: ------------------------------ Summary: AdminEvent example has redundant qualifiers. Key: CDI-433 URL: https://issues.jboss.org/browse/CDI-433 Project: CDI Specification Issues Issue Type: Clarification Reporter: John Ament Priority: Minor In the CDI 1.2 spec, the following text appears: For example, this injected Event has specified type LoggedInEvent and specified qualifier @Admin: {{@Inject @Admin Event<LoggedInEvent> any;}} The select() method returns a child Event for a given specified type and additional specified qualifiers. If no specified type is given, the specified type is the same as the parent. For example, this child Event has required type AdminLoggedInEvent and additional specified qualifier {{@Admin}}: {noformat} Event<AdminLoggedInEvent> admin = any.select( AdminLoggedInEvent.class, new AdminQualifier() ); {noformat} The problem is that the injection point any already is qualified @Admin, so the use is duplicate here. I believe the intention was that the injection point would read {{@Inject Event<LoggedInEvent> any;}} -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-432) AfterBeanDiscovery "addBean" and "addObserverMethod" operations should be queued and applied after all ABD observers are notified

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-432?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-432: ---------------------------------- http://lists.jboss.org/pipermail/cdi-dev/2014-April/005034.html > AfterBeanDiscovery "addBean" and "addObserverMethod" operations should be queued and applied after all ABD observers are notified > --------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-432 > URL: https://issues.jboss.org/browse/CDI-432 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.2.Final > Reporter: Martin Kouba > > This was originally part of the solution for CDI-392. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-432) AfterBeanDiscovery "addBean" and "addObserverMethod" operations should be queued and applied after all ABD observers are notified

by Martin Kouba (JIRA)

Martin Kouba created CDI-432: -------------------------------- Summary: AfterBeanDiscovery "addBean" and "addObserverMethod" operations should be queued and applied after all ABD observers are notified Key: CDI-432 URL: https://issues.jboss.org/browse/CDI-432 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 1.2.Final Reporter: Martin Kouba This was originally part of the solution for CDI-392. -- 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, 8 months

1
0
0 / 0

AfterBeanDiscovery in the light of CDI-392

by Martin Kouba

Hi all, I see an inconsistency between the resolution of CDI-392 and the current wording of "11.5.3. AfterBeanDiscovery event". addBean(): "Fires an event of type ProcessBean containing the given Bean and then registers the Bean with the container, thereby making it available for injection into other beans. The given Bean may implement Interceptor or Decorator." On the other hand BeanManager.getBeans() javadoc: "Note that when called during invocation of an AfterBeanDiscovery event observer, this method will only return beans discovered by the container before the AfterBeanDiscovery event is fired." It seems ProcessBean should be fired and the bean should be registred when addBean() is called BUT in the same time it should not be available via BeanManager.getBeans() until all AfterBeanDiscovery observers are processed. The same applies to observer methods. Weld 2.2.0.Final delays the ProcessBean/registration until all AfterBeanDiscovery observers are processed (note that it's not backwards compatible). I believe this is correct. If so, the AfterBeanDiscovery event description should be clarified. Otherwise the RI must be changed (and I'm afraid it wouldn't be that trivial). -- Martin Kouba Software Engineer Red Hat, Czech Republic

10 years, 8 months

3
2
0 / 0

CDI 1.2 release progress

by Antoine Sabot-Durand

Hi all, Just to keep you posted on 1.2 release evolution. Right now we are in the ballot period which ends on april 14th. There should be no problem to have a favorable result at the end of the ballot (an MR was never rejected in the JCP so far). Meanwhile there’s a lot of work to do for Weld team to finish RI, TCK and WildFly patch to release them next week. Jozef helped me this morning to release CDI 1.2 api. Artifacts are now staging in JBoss repo [1]. I published spec documentation in html [2] and pdf [3] and 1.2 javadoc as well [4]. There’ll be publicly released on tuesday or wednesday depending when JCP send us the green light. Antoine [1] https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... [2] http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html [3] http://docs.jboss.org/cdi/spec/1.2/cdi-spec-1.2.pdf [4] http://docs.jboss.org/cdi/api/1.2

10 years, 8 months

1
0
0 / 0

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

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-431?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand resolved CDI-431. -------------------------------------- Resolution: Done > 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 > Labels: Ready_to_fix > 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, 9 months

1
0
0 / 0

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

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-431?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-431: ------------------------------------- Labels: Ready_to_fix (was: ) > 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 > Labels: Ready_to_fix > 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, 9 months

1
0
0 / 0

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

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-431?page=com.atlassian.jira.plugin.sy... ] Work on CDI-431 started by Antoine Sabot-Durand. > 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 > Labels: Ready_to_fix > 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, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev April 2014