May 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Created: (CDI-121) TransactionScope

by Richard Hightower (JIRA)

TransactionScope ---------------- Key: CDI-121 URL: https://issues.jboss.org/browse/CDI-121 Project: CDI Specification Issues Issue Type: Feature Request Components: Contexts Affects Versions: 1.1 (Proposed) Environment: Java EE Reporter: Richard Hightower Priority: Minor Add TransctionalScope as a standard scope to define beans whose lifecycle is the same as a given transaction. This scope should start automatically when a transaction starts (but lazily when actually needed). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

14
47
0 / 0

[JBoss JIRA] Created: (CDI-114) Allow registration of beans at runtime

by Vincent Massol (JIRA)

Allow registration of beans at runtime -------------------------------------- Key: CDI-114 URL: https://issues.jboss.org/browse/CDI-114 Project: CDI Specification Issues Issue Type: Feature Request Components: Beans Affects Versions: 1.0 Reporter: Vincent Massol I have use cases where I need to register a bean dynamically at runtime (see the forum reference link for a detailed description of the use case). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

8
13
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-118) Standardize deployment-related exception classes

by Dan Allen (JIRA)

Standardize deployment-related exception classes ------------------------------------------------ Key: CDI-118 URL: https://issues.jboss.org/browse/CDI-118 Project: CDI Specification Issues Issue Type: Feature Request Components: Packaging and Deployment Affects Versions: 1.0 Reporter: Dan Allen Fix For: 1.1 (Proposed) While it's true that deployment exceptions are not a public API when developing with the CDI programming model, they are a public API for tools and in testing environments. It would be useful to standardize the deployment-related error and exception classes so that these tools don't have to rely on classes from the implementation. One example occurs in the CDI-TCK and it's counterpart, Arquillian. A test may want to verify that the code will result in a deployment error. Currently, to detect this exception, it's necessary to rely on an implementation specific exception class, which makes the test non-portable. Another example is a tool that starts a CDI runtime or server that provides CDI. The tool has to check for the implementation-specific exception to know if the deployment error is caused by CDI (and to capture and report that error). It important both when CDI is used for standalone bootstrap and for a container that provides CDI. Proposed APIs: javax.enterprise.inject.DeploymentException extends RuntimeException -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

6
8
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-119) Standard way to obtain a BeanManager regardless of environment

by Cloves Almeida (JIRA)

Standard way to obtain a BeanManager regardless of environment -------------------------------------------------------------- Key: CDI-119 URL: https://issues.jboss.org/browse/CDI-119 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Cloves Almeida Priority: Minor As an alternative to #CDI-117: There should be a standard way to obtain a BeanManager instance regardless of environment. I propose a BeanManagerFactory that would implement the following resolution: 1) if in a JEE environment, use the JNDI resolution already proposed on spec 2) if in a non-JEE servlet container, use the servlet context attribute as proposed in #CDI-117 3) else, fallback on a "singleton" BeanManager For extensability, one could override the resolution mechanism by providing his own BeanManagerResolver. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (CDI-116) Add programmatic API to manipulate XML metadata

by Pete Muir (JIRA)

Add programmatic API to manipulate XML metadata ----------------------------------------------- Key: CDI-116 URL: https://issues.jboss.org/browse/CDI-116 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, 3 months

1
5
0 / 0

[JBoss JIRA] Created: (CDI-133) Further clarify the notion of a decorated type

by Marius Bogoevici (JIRA)

Further clarify the notion of a decorated type ---------------------------------------------- Key: CDI-133 URL: https://issues.jboss.org/browse/CDI-133 Project: CDI Specification Issues Issue Type: Clarification Reporter: Marius Bogoevici Priority: Optional Essentially, remove the period between the first and second statement and use a single phrase instead: {quote} The set of decorated types of a decorator includes all bean types of the managed bean which are Java interfaces, except for <literal>java.io.Serializable</literal>. The decorator bean class and its superclasses are not decorated types of the decorator. {quote} This is a rather cosmetic change, but can improve the readability of the section. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
3
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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev May 2011