April 2011 - cdi-dev - Jboss List Archives

[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-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-117) Add BeanManager to a ServletContext attribute

by Christian Kaltepoth (JIRA)

Add BeanManager to a ServletContext attribute --------------------------------------------- Key: CDI-117 URL: https://issues.jboss.org/browse/CDI-117 Project: CDI Specification Issues Issue Type: Feature Request Components: Java EE integration Affects Versions: 1.0 Reporter: Christian Kaltepoth Priority: Minor CDI 1.0 defines a JNDI lookup as the standard way to obtain the BeanManager for resources not managed by the CDI environment. However in a servlet environment it would be much easier to get the BeanManager from a standardized servlet context attribute. This would be also a major simplification in environments that don't support JNDI (for example GAE) or that don't allow to use the standard JNDI name for the BeanManager (for example Apache Tomcat). This topic was already discussed on weld-dev about a year ago [1]. Weld 1.0 already supports this [2] and OpenWebBeans also added this feature [3]. Unfortunately Weld 1.1 changed the attribute to a Weld-specific name in [4] which currently leads to much confusion [5]. As both of the major CDI implementations support this feature I think it should finally be put into the spec. [1] http://lists.jboss.org/pipermail/weld-dev/2010-March/002359.html [2] https://issues.jboss.org/browse/WELD-202 [3] https://issues.apache.org/jira/browse/OWB-360 [4] https://jira.jboss.org/browse/WELD-679 [5] http://seamframework.org/Community/GettingBeanManagerFromServletContextWi... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

8
10
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

CDI 1.1

by Peter Muir

Hi everyone Welcome to the CDI 1.1 expert group. I've started to collect some resources at https://github.com/pmuir/cdi/wiki. Please take some time to read through them. I would like everyone to work their way through the various lists of issues in JIRA https://github.com/pmuir/cdi/wiki/CDI-1.1-issues and do four things: * If you are aware of an issue that is not recorded, please create one * If you think an issue on the TBC list should be addressed in CDI 1.1 then please make a note of this, and prepare an email to this list explaining why you think the issue should be included. Please restrict yourself to three such issues. * If you think an issue on the proposed list shouldn't be addressed then please make a note of this, and prepare an email to this list explaining why you think the issue shouldn't be included. Please restrict yourself to three such issues. * Write a note to the list indicating what issues you are going to take a lead on. For major issues, prepare a 2 minute summary for the concall so that you can brief people on the issue. The (soft) deadline for this exercise is Wednesday 11th May. Of course, we can continue to debate the merits of issues after this, but to make things run smoothly it will help a lot if we can get this done quickly! I propose we have conference call on Thursday 12th May to kick off, overview the main issues facing us and run through who will take what issues. Here is my proposed slot - http://www.timeanddate.com/worldclock/fixedtime.html?msg=CDI+Kick+off+con... - it's difficult to find something suitable for everyone, but this does allow both people in Australia (late night) and the US West Coast (our two extremes) to particpate. Any comments or suggestions welcome, Pete

13 years, 7 months

4
14
0 / 0

[JBoss JIRA] Created: (CDI-115) Interceptor.intercept() must throw exceptions

by Marius Bogoevici (JIRA)

Interceptor.intercept() must throw exceptions --------------------------------------------- Key: CDI-115 URL: https://issues.jboss.org/browse/CDI-115 Project: CDI Specification Issues Issue Type: Bug Components: Interceptors Affects Versions: 1.0 Reporter: Marius Bogoevici The signature of Interceptor.intercept() must allow to rethrow the checked exceptions thrown by intercepted components. Make that consistent with the other interceptor method signatures (from the interceptors spec). -- 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 April 2011