December 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-177) Clarify how default bean EL name and @Named qualifier with no value at injection point are related

by Martin Kouba (Created) (JIRA)

Clarify how default bean EL name and @Named qualifier with no value at injection point are related -------------------------------------------------------------------------------------------------- Key: CDI-177 URL: https://issues.jboss.org/browse/CDI-177 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 1.0 Reporter: Martin Kouba Related CDI 1.0 spec chapters: *2.5.2 Default bean EL names* *3.11 The qualifier @Named at injection points* -- 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, 3 months

4
12
0 / 0

[JBoss JIRA] Created: (CDI-157) Enabling/Disabling Extensions

by Pete Muir (JIRA)

Enabling/Disabling Extensions ----------------------------- Key: CDI-157 URL: https://issues.jboss.org/browse/CDI-157 Project: CDI Specification Issues Issue Type: Feature Request 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, 3 months

3
9
0 / 0

[JBoss JIRA] Created: (CDI-170) Either ditch or fix @New

by Mark Struberg (JIRA)

Either ditch or fix @New ------------------------ Key: CDI-170 URL: https://issues.jboss.org/browse/CDI-170 Project: CDI Specification Issues Issue Type: Bug Components: Concepts, Contexts Affects Versions: 1.0 Reporter: Mark Struberg Fix For: TBD The specification of @New is currently not really usable. It is really only for creating injected but unmanaged and unintercepted instances of a class. But this usecase is weird and imo just not needed. If the class under construction is an 'old' Pojo (without @Inject, etc) then it doesn't need to get managed. And it also doesn't provide any benefit over just using new Pojo(); Also you cannot @New classes which don't have a default ct. I just found no sane scenario where we cannot use a producer method instead. Can we simply deprecate @New? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

8
19
0 / 0

[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-147) Are EJB's not deployed in a bean archive eligible for CDI injection

by Stuart Douglas (JIRA)

Are EJB's not deployed in a bean archive eligible for CDI injection ------------------------------------------------------------------- Key: CDI-147 URL: https://issues.jboss.org/browse/CDI-147 Project: CDI Specification Issues Issue Type: Clarification Reporter: Stuart Douglas If an EJB is deployed in an ejb-jar without a beans.xml, is this EJB eligible for CDI injection of beans deployed in other modules? The spec says: "The container performs dependency injection on all session and message-driven bean instances, even those which are not contextual instances." To me this sounds like the intent was to allow injection into EJB's looked up from JNDI, does this also mean that EJB's in non bean archives should also be injected? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (CDI-156) Clarify that EJB3-style interceptors are applicable to CDI managed beans

by Marius Bogoevici (JIRA)

Clarify that EJB3-style interceptors are applicable to CDI managed beans ------------------------------------------------------------------------ Key: CDI-156 URL: https://issues.jboss.org/browse/CDI-156 Project: CDI Specification Issues Issue Type: Clarification Reporter: Marius Bogoevici -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
10
0 / 0

[JBoss JIRA] Created: (CDI-154) How to treat Externalizable?

by Mark Struberg (JIRA)

How to treat Externalizable? ---------------------------- Key: CDI-154 URL: https://issues.jboss.org/browse/CDI-154 Project: CDI Specification Issues Issue Type: Clarification Reporter: Mark Struberg we currently only check for Serializable and completely ignore Externalizable in the spec. Should we fix this? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (CDI-150) A beans.xml file should explicitly define its beans.xml dependencies

by Geoffrey De Smet (JIRA)

A beans.xml file should explicitly define its beans.xml dependencies -------------------------------------------------------------------- Key: CDI-150 URL: https://issues.jboss.org/browse/CDI-150 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Geoffrey De Smet See the problem described in this comment on CDI-87: https://issues.jboss.org/browse/CDI-87?focusedCommentId=12626218 Solution proposal 1: Every beans.xml gets an id: {code} <beans id="org.jboss.seam.solder"> ... </beans> {code} Then it's possible to depend on other beans.xml files: {code} <beans id="org.jboss.seam.security"> <dependency refid="org.jboss.seam.solder"/> ... </beans> {code} So when guvnor depends on security, it can automatically, transitively inherit solder (without depending on it directly): {code} <beans id="org.drools.guvnor"> <dependency refid="org.jboss.seam.security"/> ... </beans> {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (CDI-169) Remove the 'No type variable in event objects' restriction

by Stuart Douglas (JIRA)

Remove the 'No type variable in event objects' restriction ---------------------------------------------------------- Key: CDI-169 URL: https://issues.jboss.org/browse/CDI-169 Project: CDI Specification Issues Issue Type: Feature Request Affects Versions: 1.0 Reporter: Stuart Douglas CDI 10.1 states: An event object is an instance of a concrete Java class with no type variables. ... An event type may not contain a type variable. Which seems silly considering the container fires events with a type variable at startup. I can't think of any reason why this should be prohibited. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

8
15
0 / 0

[JBoss JIRA] (CDI-176) Clarify why EL name is not allowed when declaring resource

by Martin Kouba (Created) (JIRA)

Clarify why EL name is not allowed when declaring resource ---------------------------------------------------------- Key: CDI-176 URL: https://issues.jboss.org/browse/CDI-176 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 1.0 Reporter: Martin Kouba CDI 1.0 spec states in section *3.5.1. Declaring a resource*: "If the producer field declaration specifies an EL name, the container automatically detects the problem and treats it as a definition error." Is there any reason to forbid EL name for declared resource? -- 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, 3 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev December 2011