March 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Created: (CDI-110) Allow proxying of abstract classes (Service Handler)

by George Gastaldi (JIRA)

Allow proxying of abstract classes (Service Handler) ---------------------------------------------------- Key: CDI-110 URL: https://issues.jboss.org/browse/CDI-110 Project: CDI Specification Issues Issue Type: Feature Request Components: Inheritance and Specialization Affects Versions: 1.1 (Proposed) Reporter: George Gastaldi According to mojavelinux: {quote} <mojavelinux> service handler, interceptors and decorators are all complementary <mojavelinux> and cdi is missing the first...which we now realize {quote} CDI 1.1 should provide a way to inject abstract classes by specifying a ServiceHandler (Check http://docs.jboss.org/seam/3/solder/latest/reference/en-US/html/serviceha...) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

10
34
0 / 0

[JBoss JIRA] Created: (CDI-103) Support client controlled contexts

by Pete Muir (JIRA)

Support client controlled contexts ---------------------------------- Key: CDI-103 URL: https://issues.jboss.org/browse/CDI-103 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Pete Muir In a client controlled context, the client controls via some identifier (probably an identifier, but we should allow the context to inspect the injection point) which contextual instances it sees for a particular bean type. For example given: {code} @MyScope class Foo { String name; } {code} and a context which uses annotations to differentiate between contextual instance, these two injection points would see different instances: {code} @Inject @Bar Foo barFoo; @Inject @Baz Foo bazFoo; {code} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (CDI-109) Invalid beans should not be injectable into extensions

by John Ament (JIRA)

Invalid beans should not be injectable into extensions ------------------------------------------------------ Key: CDI-109 URL: https://issues.jboss.org/browse/CDI-109 Project: CDI Specification Issues Issue Type: Feature Request Reporter: John Ament Currently, you can inject beans that may not be ready yet into the extension's call back methods. As an example, I can inject something application scoped like this in to an extension, but it should really be throwing a definition exception (or similar): public void handleABD(@Observes AfterBeanDiscovery abd, MyApplicationScopedBean masb) { } Pete had noted that really the only safe thing to inject, other than the observed call back, is the bean manager. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

10
18
0 / 0

[JBoss JIRA] Created: (CDI-112) Clarify how alternatives are enabled

by Shane Bryzak (JIRA)

Clarify how alternatives are enabled ------------------------------------ Key: CDI-112 URL: https://issues.jboss.org/browse/CDI-112 Project: CDI Specification Issues Issue Type: Clarification Components: Beans Affects Versions: 1.0 Reporter: Shane Bryzak The spec is open to interpretation about how alternatives are enabled. One popular interpretation is that alternatives must be enabled within the same bean archive that contains the alternative bean. However, it might be worth considering the merit of enabling an alternative from a deployment archive that contains the bean archive. For example, suppose we have the following deployment archive: foo.war /WEB-INF beans.xml /lib bar.jar /META-INF beans.xml /com /acme AlternativeBean.class It may be worth allowing AlternativeBean.class (a class annotated with @Alternative) to be enabled by listing it in the <alternatives> section of foo.war/WEB-INF/beans.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
8
0 / 0

calling 'equals' on a proxy?

by Mark Struberg

Hi Pete, others! Do you remember our discussion about what should happen if equals() gets called on a proxy? Should it route to the equals method of the currently proxied instance? LieGrue, strub

13 years, 2 months

7
18
0 / 0

[JBoss JIRA] Created: (CDI-108) Align with release of @Inject included in the Java EE 7 platform

by Pete Muir (JIRA)

Align with release of @Inject included in the Java EE 7 platform ---------------------------------------------------------------- Key: CDI-108 URL: https://issues.jboss.org/browse/CDI-108 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Pete Muir There is likely to be an update to JSR-330, @Inject, which we should align with. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (CDI-107) Provide automatic startup capabilities for beans.

by John Ament (JIRA)

Provide automatic startup capabilities for beans. ------------------------------------------------- Key: CDI-107 URL: https://issues.jboss.org/browse/CDI-107 Project: CDI Specification Issues Issue Type: Feature Request Reporter: John Ament Certain beans (such as @ApplicationScoped or @Singleton) should be able to be instantiated on startup of the application automatically, similar to EJB3.1's @Startup. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (CDI-106) Support JMS mappings

by Pete Muir (JIRA)

Support JMS mappings -------------------- Key: CDI-106 URL: https://issues.jboss.org/browse/CDI-106 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Pete Muir -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
11
0 / 0

[JBoss JIRA] Created: (CDI-105) Provide a means for portable extensions to access beans.xml files

by Stuart Douglas (JIRA)

Provide a means for portable extensions to access beans.xml files ----------------------------------------------------------------- Key: CDI-105 URL: https://issues.jboss.org/browse/CDI-105 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Stuart Douglas There is currently no portable way for extensions to get access to beans.xml files installed in WEB-INF/lib, as CDI starts up before the ServletContext is availible. This would be useful for extensions that wish to add extra information to beans.xml in a different namespace. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
16
0 / 0

[JBoss JIRA] Created: (CDI-111) ValidationFactory -> ValidatorFactory

by Mark Struberg (JIRA)

ValidationFactory -> ValidatorFactory ------------------------------------- Key: CDI-111 URL: https://issues.jboss.org/browse/CDI-111 Project: CDI Specification Issues Issue Type: Clarification Components: Concepts Reporter: Mark Struberg Priority: Minor The CDI-1.0 spec mentions a ValidationFactory, but such a class doesn't exist in JSR-303. Guess Gavin meant the ValidatorFactory. (catched by Matt Benson) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev March 2011