April 2017 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-700) BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation

by John Ament (JIRA)

[ https://issues.jboss.org/browse/CDI-700?page=com.atlassian.jira.plugin.sy... ] John Ament commented on CDI-700: -------------------------------- The title of this ticket mentions "AfterDeploymentValidation" - this should be allowable. The body of this ticket mentions "AfterBeanDiscovery" - this should not be allowable. Agree? > BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation > ---------------------------------------------------------------------------------- > > Key: CDI-700 > URL: https://issues.jboss.org/browse/CDI-700 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > Spec doesn't say anything about it and javadoc allows its usage in {{AfterBeanDiscovery}} observers. > The method should also be listed in section 11.3 related to {{BeanManager}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-700) BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-700?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-700: ------------------------------------------ During 1.2 discussion we decided to allow some {{BeanManager}} methods to be called during {{AfterBeanDiscovery}} observer invocation. These was not allowed in CDI 1.1. But as Martin said, we agreed that {{getReference}} and {{getInjectablereference}} couldn't be called before {{AfterDeploymentValidation}}. As createInstance() provides something similar, I find consistent to limit its usage in the same way. The rule being: you can't request a bean instance before {{AfterDeploymentValidation}}. That makes sense since custom context are registered with this observer. > BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation > ---------------------------------------------------------------------------------- > > Key: CDI-700 > URL: https://issues.jboss.org/browse/CDI-700 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > Spec doesn't say anything about it and javadoc allows its usage in {{AfterBeanDiscovery}} observers. > The method should also be listed in section 11.3 related to {{BeanManager}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-700) BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-700?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-700: ------------------------------------- Fix Version/s: 2.0 .Final > BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation > ---------------------------------------------------------------------------------- > > Key: CDI-700 > URL: https://issues.jboss.org/browse/CDI-700 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > Spec doesn't say anything about it and javadoc allows its usage in {{AfterBeanDiscovery}} observers. > The method should also be listed in section 11.3 related to {{BeanManager}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-700) BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation

by John Ament (JIRA)

[ https://issues.jboss.org/browse/CDI-700?page=com.atlassian.jira.plugin.sy... ] John Ament commented on CDI-700: -------------------------------- After you talking about {{AfterBeanDiscovery}} or {{AfterDeploymentValidation}}? > BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation > ---------------------------------------------------------------------------------- > > Key: CDI-700 > URL: https://issues.jboss.org/browse/CDI-700 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Antoine Sabot-Durand > > Spec doesn't say anything about it and javadoc allows its usage in {{AfterBeanDiscovery}} observers. > The method should also be listed in section 11.3 related to {{BeanManager}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-700) BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/CDI-700?page=com.atlassian.jira.plugin.sy... ] Matej Novotny commented on CDI-700: ----------------------------------- I, on the other hand, fully agree. Current state doesn't make sense and this issue looks like a mere overlook in the spec/doc. {{BeanManager.getReference}} should have the same limitations as {{BeanManager.createInstance}} as they can be used in similar manner. I would be weird if you could use one but were prohibited from using the other to achieve the same goal. After all {{BeanManger.createInstance}} is a sort of shorcut from having to create creational context, bean attributes, bean itself and then getting a reference. > BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation > ---------------------------------------------------------------------------------- > > Key: CDI-700 > URL: https://issues.jboss.org/browse/CDI-700 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Antoine Sabot-Durand > > Spec doesn't say anything about it and javadoc allows its usage in {{AfterBeanDiscovery}} observers. > The method should also be listed in section 11.3 related to {{BeanManager}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-700) BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-700?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-700: ---------------------------------- Note that {{BeanManager.getReference()}} and {{BeanManager.getInjectableReference()}} are not allowed during {{AfterBeanDiscovery}} either. And I think it's for a good reason. At this time an extension can still affect the resolution. Thus the result of {{BeanManager.createInstance().select(Foo.class)}} during {{AfterBeanDiscovery}} might be different than the result in runtime. > BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation > ---------------------------------------------------------------------------------- > > Key: CDI-700 > URL: https://issues.jboss.org/browse/CDI-700 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Antoine Sabot-Durand > > Spec doesn't say anything about it and javadoc allows its usage in {{AfterBeanDiscovery}} observers. > The method should also be listed in section 11.3 related to {{BeanManager}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-700) BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation

by John Ament (JIRA)

[ https://issues.jboss.org/browse/CDI-700?page=com.atlassian.jira.plugin.sy... ] John Ament commented on CDI-700: -------------------------------- I disagree - I think it should be useable! > BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation > ---------------------------------------------------------------------------------- > > Key: CDI-700 > URL: https://issues.jboss.org/browse/CDI-700 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Antoine Sabot-Durand > > Spec doesn't say anything about it and javadoc allows its usage in {{AfterBeanDiscovery}} observers. > The method should also be listed in section 11.3 related to {{BeanManager}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-700) BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation

by Antoine Sabot-Durand (JIRA)

Antoine Sabot-Durand created CDI-700: ---------------------------------------- Summary: BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation Key: CDI-700 URL: https://issues.jboss.org/browse/CDI-700 Project: CDI Specification Issues Issue Type: Clarification Reporter: Antoine Sabot-Durand Spec doesn't say anything about it and javadoc allows its usage in {{AfterBeanDiscovery}} observers. The method should also be listed in section 11.3 related to {{BeanManager}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

CDI.current() in AfterDeploymentValidation

by John Ament

So I know during the reception of AfterDeploymentValidation, the container isn't fully bootstrapped. However, its valid to look up beans. I would therefore expect that CDI.current().select()... to work fine. However, at least in Weld it doesn't. This is because CDI.current() cannot figure out what container to use (it's not fully bootstrapped yet). So my question - is this a Weld issue, or a spec clarification? John ________________________________ NOTICE: This e-mail message and any attachments may contain confidential, proprietary, and/or privileged information which should be treated accordingly. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this message, and destroy all physical and electronic copies. Thank you.

7 years, 8 months

3
6
0 / 0

help me make my decision

by antoine

Dear, I wanted to ask you to help me decide which phone to choose, please see the options here http://nycpowerwashing.com/obviously.php?bfbe. Thank you! Warmly, antoine

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev April 2017