September 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Commented: (CDI-92) Allow injection of Bean object for a bean

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-92?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-92: ------------------------------ This is a good idea, however I think we need to introduce a qualifier - {{@Delegate}} is not a qualifier. Any ideas on name? > Allow injection of Bean object for a bean > ----------------------------------------- > > Key: CDI-92 > URL: https://issues.jboss.org/browse/CDI-92 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-53) Datasources and other resources defined on alternatives

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-53?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-53: ------------------------- Summary: Datasources and other resources defined on alternatives (was: Datasources defined on alternatives) Forum Reference: http://www.seamframework.org/Weld/JavaEEIntegrationWishlist#H-TtDataSourc... (was: http://www.seamframework.org/Weld/JavaEEIntegrationWishlist#H-TtDataSourc...) > Datasources and other resources defined on alternatives > ------------------------------------------------------- > > Key: CDI-53 > URL: https://issues.jboss.org/browse/CDI-53 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Priority: Minor > Fix For: 1.1 (Proposed) > > > http://download.oracle.com/javaee/6/api/javax/annotation/sql/DataSourceDe... -- if this is used on an alternative class, only enable it if the alternative is enabled. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-80) Support conversations in Servlet

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-80?page=com.atlassian.jira.plugin.sys... ] Jozef Hartinger commented on CDI-80: ------------------------------------ Why is the conversation propagation limited to *GET* request parameter only? If I got it right this rule prevents form-processing servlet-only applications from using the conversation scope. > Support conversations in Servlet > -------------------------------- > > Key: CDI-80 > URL: https://issues.jboss.org/browse/CDI-80 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts, Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > > In CDI 1.0, the Conversation Scope has extremely limited availability. It is accessible from after RESTORE_VIEW phase in JSF, to the end of the Response, but this is extremely limiting, and in fact does not even address all use-cases within JSF. > For instance: > User has custom PhaseListener for Before RESTORE_VIEW phase, or user has custom PhaseListener that invokes before ConversationPhaseListener. > In said PhaseListener, user attempts to access a ConversationScoped bean. > ContextNotActiveException results, even though there may be a valid CID in the Request URL > Example 2: > User attempts to access ConversationScope outside of the JSF lifecycle (Via EL in a Servlet or ServletFilter, for instance.) > ContextNotActiveException results, this just doesn't work! > There is no reason why the ConversationScope should be any less available than the RequestScope, since both depend on the same underlying context objects. (Request, Session, etc) > ConversationScope should be ubiquitous in the Servlet Container Request/Response lifecycle. This will greatly improve ability to use CDI in view/web frameworks other than JSF. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-86) Support firing general purpose lifecycle events in Java EE environments

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-86?page=com.atlassian.jira.plugin.sys... ] Jozef Hartinger commented on CDI-86: ------------------------------------ The pull request uses ConversationContext.class as a value for the @Initialized and @Destroyed qualifiers while it should use ConversationScoped.class > Support firing general purpose lifecycle events in Java EE environments > ----------------------------------------------------------------------- > > Key: CDI-86 > URL: https://issues.jboss.org/browse/CDI-86 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-86) Support firing general purpose lifecycle events in Java EE environments

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-86?page=com.atlassian.jira.plugin.sys... ] Jozef Hartinger commented on CDI-86: ------------------------------------ {quote}Jozef, can you spin the idea about extending this to non-built-in scopes to a new issue please?{quote} CDI-165 > Support firing general purpose lifecycle events in Java EE environments > ----------------------------------------------------------------------- > > Key: CDI-86 > URL: https://issues.jboss.org/browse/CDI-86 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-92) Allow injection of Bean object for a bean

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-92?page=com.atlassian.jira.plugin.sys... ] Jozef Hartinger commented on CDI-92: ------------------------------------ It seems that for an interceptor / decorator the injected object would be an instance of javax.enterprise.inject.spi.Interceptor/Decorator. Could we rather: 1) state explicitly that a bean representing intercepted / decorated instance should be injected or 2) support @Inject @Delegate Bean<?> > Allow injection of Bean object for a bean > ----------------------------------------- > > Key: CDI-92 > URL: https://issues.jboss.org/browse/CDI-92 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (CDI-142) Clarify behaviour of specializing beans across bean archive boundaries

by Stuart Douglas (JIRA)

Clarify behaviour of specializing beans across bean archive boundaries ---------------------------------------------------------------------- Key: CDI-142 URL: https://issues.jboss.org/browse/CDI-142 Project: CDI Specification Issues Issue Type: Clarification Reporter: Stuart Douglas For instance, if a bean in a war specializes a bean in an ejb jar does the bean in the war become visible to other bean archives that would not normally be able to see it? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
9
0 / 0

[JBoss JIRA] Commented: (CDI-61) Producers and beans that are under construction

by Mark Struberg (JIRA)

[ https://issues.jboss.org/browse/CDI-61?page=com.atlassian.jira.plugin.sys... ] Mark Struberg commented on CDI-61: ---------------------------------- We had a bug report last year that one tried to use BeanA, BeanB and in the @PostConstruct and @Inject codes he used methods from the other bean. This is almost the same imo and there is already a language for it which says that a contextual instance is only put into service once it's finally contructed. But I can't find it quickly :/ > Producers and beans that are under construction > ----------------------------------------------- > > Key: CDI-61 > URL: https://issues.jboss.org/browse/CDI-61 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Proposed) > > > I think we need the spec to say something about cases where an injection point of a bean resolves to a producer method of the same bean. The implementation should detect that this is a definition error. It shouldn't try to call a producer method on a non-fully-initialized bean. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-1) Clarify how resource producer fields (for persistence contexts) interact with transaction propagation

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/CDI-1?page=com.atlassian.jira.plugin.syst... ] Stuart Douglas commented on CDI-1: ---------------------------------- I think this is sufficient. > Clarify how resource producer fields (for persistence contexts) interact with transaction propagation > ----------------------------------------------------------------------------------------------------- > > Key: CDI-1 > URL: https://issues.jboss.org/browse/CDI-1 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Proposed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-61) Producers and beans that are under construction

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/CDI-61?page=com.atlassian.jira.plugin.sys... ] Stuart Douglas commented on CDI-61: ----------------------------------- This may not actually be a problem, if the injected bean is normal scoped and the producer does not attempt to call any methods on the injected proxy, although this sort of setup should probably be avoided anyway. > Producers and beans that are under construction > ----------------------------------------------- > > Key: CDI-61 > URL: https://issues.jboss.org/browse/CDI-61 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Proposed) > > > I think we need the spec to say something about cases where an injection point of a bean resolves to a producer method of the same bean. The implementation should detect that this is a definition error. It shouldn't try to call a producer method on a non-fully-initialized bean. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev September 2011