October 2012 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-89) Add @Unwraps from Seam Solder

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-89?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-89: ------------------------- Fix Version/s: TBD (was: 1.1.PRD) > Add @Unwraps from Seam Solder > ------------------------------ > > Key: CDI-89 > URL: https://issues.jboss.org/browse/CDI-89 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts > Affects Versions: 1.0 > Reporter: Stuart Douglas > Assignee: Pete Muir > Fix For: TBD > > > @Unwraps allows for an essentially stateless scope for producer methods and fields. > At injection time a dependent scoped proxy is injected into the injection point. When a methods is invoked on this proxy it calls the corresponding @Unwraps methods to get the instance to invoke the method on. > Because the proxy is @Dependent scoped, the @Unwraps method can inject the corresponding InjectionPoint. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-77) Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-77?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-77: ------------------------- Fix Version/s: TBD (was: 1.1 (Proposed)) Forum Reference: http://lists.jboss.org/pipermail/weld-dev/2010-April/002441.html (was: http://lists.jboss.org/pipermail/weld-dev/2010-April/002441.html) Defer, this isn't that important and there isn't agreement on it. > Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans > ---------------------------------------------------------------------------------------------------- > > Key: CDI-77 > URL: https://issues.jboss.org/browse/CDI-77 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: TBD > > > for example > class Foo { > @Inject Bar bar; > } > class bar { > @Inject Foo foo; > } -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-75) Clarify what happens to a bean which belongs to inactive when it observes an event

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-75?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-75: ------------------------- Fix Version/s: 1.1 (Proposed) (was: 1.1.PRD) Forum Reference: http://lists.jboss.org/pipermail/weld-dev/2010-April/002425.html (was: http://lists.jboss.org/pipermail/weld-dev/2010-April/002425.html) > Clarify what happens to a bean which belongs to inactive when it observes an event > ---------------------------------------------------------------------------------- > > Key: CDI-75 > URL: https://issues.jboss.org/browse/CDI-75 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Events > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Proposed) > > -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-203) Decorator support for @MessageDriven bean MessageListener interface

by David Blevins (Created) (JIRA)

Decorator support for @MessageDriven bean MessageListener interface ------------------------------------------------------------------- Key: CDI-203 URL: https://issues.jboss.org/browse/CDI-203 Project: CDI Specification Issues Issue Type: Feature Request Components: Decorators, Java EE integration Affects Versions: 1.1 (Proposed) Reporter: David Blevins Interceptors message-driven beans are explicitly mentioned as supported in CDI 1.0, but decorator support appears to be clearly left out. Decorators that implement the message listener interface would be very useful. As well, most contains have one stack now that does both interceptors and decorators, so enabling this for MDBs would be quite easy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

4
12
0 / 0

[JBoss JIRA] (CDI-186) Interceptor bindings need clarification

by Jozef Hartinger (Created) (JIRA)

Interceptor bindings need clarification --------------------------------------- Key: CDI-186 URL: https://issues.jboss.org/browse/CDI-186 Project: CDI Specification Issues Issue Type: Clarification Components: Interceptors Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Fix For: 1.1.EDR2 As part of CDI-2, changes were made to the Interceptors chapter of the CDI specification. These changes need further clarification: {quote} Interceptor bindings defined on methods may override the interceptor bindings defined on classes. {quote} One way to interpret this is that the set of interceptor bindings defined on a method overrides the set of interceptor bindings defined on a class, which is clearly not the intended behavior. {quote} If the set of interceptor bindings of a bean or interceptor, including bindings inherited from stereotypes and other interceptor bindings, has two instances of a certain interceptor binding type and the instances have different values of some annotation member, the bean or interceptor must override the *inherited set* by definining an annotation instance of its own, otherwise, the container automatically detects the problem and treats it as a definition error. {quote} Here again I would avoid referencing "the inherited set", since it's not clear what that means, and rather use wording similar to the section 2.4.4 - default scope of a stereotype. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (CDI-127) Add support for annotation scanning of Java enums

by Brian Leathem (JIRA)

Add support for annotation scanning of Java enums ------------------------------------------------- Key: CDI-127 URL: https://issues.jboss.org/browse/CDI-127 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Brian Leathem It would be useful if Java enums were included in the CDI annotation scan. A use case for this is found in the Seam Faces project, where we would like to use annotations on enums for configuration purposes. The annotation would look like: @ViewConfig public enum Pages { ... } It is my understanding that the current CDI specification (1.0) does not require scanning of the enum and will not pick up the @ViewConfig annotation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

4
12
0 / 0

[JBoss JIRA] (CDI-269) Fire ProcessAnnotatedType for annotations

by Pete Muir (JIRA)

Pete Muir created CDI-269: ----------------------------- Summary: Fire ProcessAnnotatedType for annotations Key: CDI-269 URL: https://issues.jboss.org/browse/CDI-269 Project: CDI Specification Issues Issue Type: Bug Affects Versions: 1.1.EDR Reporter: Pete Muir Assignee: Pete Muir Fix For: 1.1 (Proposed) If we fire a PAT event for annotations, the members can have @Nonbinding added -- 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

12 years, 2 months

1
2
0 / 0

[JBoss JIRA] (CDI-15) Relax @Target annotation for CDI Scopes and Qualifiers

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-15?page=com.atlassian.jira.plugin.sys... ] Pete Muir resolved CDI-15. -------------------------- Resolution: Done > Relax @Target annotation for CDI Scopes and Qualifiers > ------------------------------------------------------ > > Key: CDI-15 > URL: https://issues.jboss.org/browse/CDI-15 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts > Affects Versions: 1.0 > Reporter: Stuart Douglas > Assignee: Pete Muir > Fix For: 1.1.PRD > > > In some cases it may make sense to apply a scope or qualifier in a place that was not envisaged by the spec but that would be useful for a portable extension. > For example, the @Constructs extension described at > http://www.seamframework.org/Weld/PortableExtensionsPackage#H-BeanDeclara... > is not possible because scopes and qualifiers can not be placed on constructors -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-273) Clarify that CDI does not use standard APIs to remove a SFSB

by arjan tijms (JIRA)

arjan tijms created CDI-273: ------------------------------- Summary: Clarify that CDI does not use standard APIs to remove a SFSB Key: CDI-273 URL: https://issues.jboss.org/browse/CDI-273 Project: CDI Specification Issues Issue Type: Clarification Components: Java EE integration Affects Versions: 1.1 (Proposed) Reporter: arjan tijms By applying a scope to a Stateful Session Bean, CDI gets the responsibility to at some point destroy this SFSB (when the scope ends). However, destroying a SFSB other then by calling a method annotated with `@Remove` is not something a user can normally do. There is no standard API for this in EJB. CDI is capable of doing this by calling into implementation specific EJB APIs, but this is not overly clear when reading the spec and could be clarified. -- 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

12 years, 2 months

2
2
0 / 0

[JBoss JIRA] (CDI-276) Clarify that scope annotations shouldn't be used at injection points

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-276?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-276: -------------------------- Fix Version/s: 1.1 (Proposed) > Clarify that scope annotations shouldn't be used at injection points > -------------------------------------------------------------------- > > Key: CDI-276 > URL: https://issues.jboss.org/browse/CDI-276 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Contexts > Reporter: Nicklas Karlsson > Fix For: 1.1 (Proposed) > > > Sometimes you see people trying to do > @Inject @ApplicationScoped > private SomeRequestScopedBean sRSB; > It should be clarified that this has no effect. Could even throw a validation exception at deployment. -- 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

12 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev October 2012